Fix Google Crawler Issues #93
Labels
Comments
|
Google is not crawling CMS.js correctly as seen in the "fetch as google" image below. We may have to implement a dynamic renderer or prerenderer as a dependency as seen here. Exploring options... SEO optimization and crawling issues are also related to #24 and #61.
|
This was referenced Dec 23, 2018
Closed
Closed
|
Also need to use history mode, crawler don't crawl the hash url. |
cdp1337
added a commit
to cdp1337/markdownmaster
that referenced
this issue
Nov 8, 2022
Fixes: Images/hyperlinks within meta tags chrisdiana/cms.js#95 Google crawler issues chrisdiana/cms.js#93 URLs using history instead of hashes chrisdiana/cms.js#80 Also: Embedded marked in the example as a default option for users Implement github CI on pushes to verify repo Include example site in deployed package Switch onroute and onload to be separate methods outside of the config object Add dynamic page titles based on content Add dynamic Last-Modified headers for automatic post dates Add support for nested content Add support for paths in the URL Retool search to support searching body content Add method to retrieve all tags for a given collection Add SEO-specific page title (text that displays in the browser for the page) Add support for images within metadata (goes along with the bugfix) Fix onroute to only be called AFTER the content has been rendered Add debug logging method
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Verify Google is crawling CMS.js dynamic views correctly.
The text was updated successfully, but these errors were encountered: