Will disabling javascript be considered as cloaking by Google

Will disabling javascript be considered as cloaking by Google - Google Search Console is a free application that allows you to identify, troubleshoot, and resolve any issues that Google may encounter as it crawls and attempts to index your website in search results. If you’re not the most technical person in the world, some of the errors you’re likely to encounter there may leave you scratching your head. We wanted to make it a bit easier, so we put together this handy set of tips about seo, google-search, static-content, cloaking to guide you along the way. Read the discuss below, we share some tips to fix the issue about Will disabling javascript be considered as cloaking by Google.Problem :


There is a site with dynamic content generation (angular). Google is not indexing it well. But it is indexed well with static pages (same content). Static pages are not fast because of page reloading each time. If I will render static pages only for Google (IPs,bots, google-analytics disabled) - will it be considered as cloaking (same content for human and the same DOM after load(just without script tags))?


Solution :

If you remove the JavaScript from the page based on IP, User Agent or any other method that detects Google, then yes its cloaking.



Treat Google like any other user. Angular websites are indexable just fine, its used by thousands of websites, I recommend that you dig deeper into your research on getting dynamic content seen.


If the issue about seo, google-search, static-content, cloaking is resolved, there’s a good chance that your content will get indexed and you’ll start to show up in Google search results. This means a greater chance to drive organic search traffic to your site.

Comments

Popular posts from this blog

Years after news site changed name, Google is appending the old name to search titles and news stories

Load Wikipedia sourced biographies via Ajax or render it with the rest of the page as part of the initial request?

SEO: change site address from http://www. to https://