StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3981306
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-10-20T18:55:46.400
FavoriteCount
0
LastActivityDate
2010-10-20T18:55:46.400
LastEditDate
LastEditorUserId
0
OwnerUserId
16883
ParentId
3980970
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Don't rely on what the search engine may do in this regard. You want all versions to be crawled. To achieve that: <ul> <li>Have different URLs for the different language versions. </li> <li>Make sure the search engines can find the different versions.</li> </ul> Overall, I believe that the way I did it on <a href="http://www.brazzy.de/" rel="nofollow">my homepage</a> is close to ideal in regard to both search engines and regular users: <ul> <li>When a user arrives at, e.g. brazzy.de/index.php, the site tries to determine the language from cookie (if present) or browser settings (Accept-language header), defaults to English, and does not redirect</li> <li>Every page has links to the different language versions of that page (IMO the most important factor for user convenience, and also makes sure search engines can easily find the different versions).</li> <li>These links lead to e.g. brazzy.de/en/index.php, which is in my case rewritten to brazzy.de/index.php?lang=en - this ensures that search engines see distinct URLs for the different language versions.</li> <li>Visiting such a subdirectory sets the language cookie to that language</li> <li>The pages without a language-specific URL (i.e. where the language depends on client data) use e.g. <code><link rel="canonical" href="/en/"></code> to tell the search engine at which language-specific URL that page can be found.</li> <li>Use <a href="http://en.wikipedia.org/wiki/Sitemaps" rel="nofollow">XML sitemaps</a> to further make sure search engines can find all pages and all different language versions.</li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow Do Search Engines See A Localized Django Site?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMichael Borgwardt
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow Do Search Engines See A Localized Django Site?
 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
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

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.