Debugging how Google renders your site’s page

[tasmih1234]

Splitt immediately answers the most crucial question, “How do I know if it’s a JavaScript problem?”

Martin advises debugging rendering issues by first checking Google Search Console, which shows what Google saw when it crawled your web page.

Google explains rendering relative to JavaScript as:

“JavaScript loads additional content when the page is open in a browser. This is called client-side rendering. Google Search sees this content along with the content in the HTML of a website.”
Splitt explains that by using Google Search Console, you can inspect your URL and use the rendered HTML to identify if certain parts of a page don’t render because, as he says:

“Use that rendered HTML as your source of truth; that’s what belarus mobile numbers list Google Search sees when it comes to this URL, and whatever is there is there.”
Martin also advised:

“If your content is there (Google Search Console) and it’s what you expect it to be, then it’s very likely not going to be JavaScript, which is causing the problem.”
He added:

“If people were doing that, just that, which I think is very basic, 90% of the people showing up in my inbox would not show up; that’s what I would do.”
Splitt also recommends using Google Rich Results Test and Chrome Dev Tools to debug JavaScript issues.

You can see Martin’s tips for debugging JavaScript in his presentation below.