-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SEO: resolve potential duplicite content #19
Comments
|
Ultimately, I think C) meta "canonical" should be added to every page to resolve any potential duplicate content we might miss... (E.g. tracking campaigns and traffic sources) |
I wrote a simple PHP function that rewrites any url into a "canonical url". If "echo get_canonical_meta($url)" can be added into every page , it can help us explain to search engines our duplicite content. |
Unfortunately, the application is written in Python, so we can not include your script into every page view directly. On the other hand, I assume we are able to rewrite it into Python (@slaweet?) |
I added canonical urls (f9a7454). |
As for disallowing /en/ and /cs/ I removed it from robots.txt, but I don't see why it should influence page rank of any other page then the ones with /en/ and /cs/, which we don't want in search results anyway. And IMO we don't want Google to see the redirect, but directly the alternative language version through |
OK. The canonical form of the url is also related to |
I've updated |
Thank you, Víťo. |
I might be too picky, but other potential duplicate content is |
view-source:https://anatom.cz/ for logged in users actually redirects to view-source:https://anatom.cz/overview (notice address bar). Hopefully, search engines cannot log in :-) I use www.google.com/webmasters/tools/ every now and then, I haven't noticed any SEO warnings or errors there. I've linked Webmaster tools with GA, so it probably displays the errors in GA as well. Ad 4 and 5: I see the problem, I'll have to think about how to solve it technically. |
Although there is no link to such a page, not sure if this could be problem for search engines or users/brand/security: |
Re #19 (comment): The problem is that we don't do the check if the given string is a valid username. If not, then the page should return an error. |
Víťo, when I suggested to make a separate url for /overview/?tab=location in order to get the crawler see our main content tree, I didn't know that google can understand AJAX. |
Marku, I don't think Google AJAX crawling scheme is applicable here. Anything we want to appear in search results (like /overview/?tab=location) has to be on a separate url. |
And FYI, your example with "Vítá vás blbeček" has been indexed by google as Google crawled our Github :-) |
First, I am concerned we have very similar content (and identical ) when user view in image under different chapters/body parts (eg. practiceanatomy.com/view/UE/image/casti-lidskeho-telasvg and practiceanatomy.com/view/LE/image/casti-lidskeho-telasvg). Can we change the url to practiceanatomy.com/view/LE/#image/casti-lidskeho-telasvg or practiceanatomy.com/view/LE/#image/5 ? Second, I've found a simple SEO guide, and there are several things we do not do yet:
|
Several examples of potential duplicite content exist:
Duplicite content should be a) avoided if possible, b) resolved by redirect 301, or C) resolved by <link rel="canonical" (https://support.google.com/webmasters/answer/139066).
The text was updated successfully, but these errors were encountered: