StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15210721
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-03-04T20:40:47.703
FavoriteCount
0
LastActivityDate
2013-03-04T22:28:17.213
LastEditDate
2013-03-04T22:28:17.213
LastEditorUserId
1145388
OwnerUserId
1145388
ParentId
15207333
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
This kind of thing happens. Its easier than you think to create a bad link. One hard coded domain name in the wrong place and you have a link to somewhere you didn't mean to link. Once Googlebot finds a site served on a wrong domain, it will crawl the whole thing. Even if you are correct, that you would never create such a link, maybe there is an external link created by a user in which they got the domain name confused. The technique that you need to apply is called URL canonicalization. You have two options: <ul> <li>Put the rel canonical meta tag on each of your pages. <code>search/de-de/gebaude/fenster/77/1/</code> would have a canonical URL in the tag which has the correct domain: <code>http://www.example.de/search/de-de/gebaude/fenster/77/1/</code> You'd have to make sure that the domain in the canonical tag is the <code>.de</code> domain whether that page were accessed on the <code>.co.uk</code> domain or on the <code>.de</code> domain.</li> <li>Use 301 redirects to correct any URLs that are wrong. Have your server detect that a domain name is wrong. 301 redirect <code>www.example.co.uk/search/de-de/gebaude/fenster/77/1/</code> to <code>www.example.de/search/de-de/gebaude/fenster/77/1/</code></li> </ul> Another random piece of SEO advice: I would remove the word "search" from your URLs. Google doesn't like to index site search results in its search results. I've seen cases where it assumes that the word "search" in the URL indicates that the page shouldn't be indexed for this reason.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POGoogle indexing only specific domain
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USStephen Ostermiller
UserOwnerUserId
1. USStephen Ostermiller
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POGoogle indexing only specific domain
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COChecked everything and did by your answer, working much better now, thank you!
 singulars
 PostPostId
 PO
 UserUserId
 USfalnyr

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.