Skip to content
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

Using gh-pages example, lost SEO #45

Closed
overshard opened this issue May 10, 2012 · 3 comments
Closed

Using gh-pages example, lost SEO #45

overshard opened this issue May 10, 2012 · 3 comments

Comments

@overshard
Copy link
Contributor

Using the method suggested for gh-pages you really lose/don't get any SEO benefit. Search engines basically see it as a blank page. I'm instead generating the page and copying over the HTML, maybe this should be the suggested method?

@jeromegn
Copy link
Owner

It's not perfect indeed.

Crawlers do index it though: https://developers.google.com/search-appliance/documentation/68/admin_crawl/AdvancedTopics#documentwrite

@overshard
Copy link
Contributor Author

I know on Pinry when I switched over to the documentup.min.js file on gh-pages it basically got dropped from Google search results entirely. When I copied and pasted over the DocumentUp code it showed back up... Maybe you are using doesn't work because for one you are using a separate JS file, not inline, and it's pulling a page and then writing. From what this is saying I don't think it will take into account you pulling a documentup page then writing it.

@jeromegn
Copy link
Owner

The gh-pages thing is all JS and search engines don't really index that quite well yet (3 years later). Ideally I'll add a feature like allowing CNAMEs (like Github) and that should work better.

However, I think Google is now indexing JS-generated pages properly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants