Google provides recommendations for identifying technical SEO issues impacting indexing and ranking.
Three Techniques to Resolve Technical Problems
Google suggests three effective techniques for tackling technical issues:
- Verify if the page is indexed or indexable.
- Confirm whether the page is duplicated or if another page serves as the canonical.
- Scrutinize rendered HTML for code-related issues.
1. Assessing URL Indexability: Vital Checks
One often overlooked yet crucial aspect is the indexability of a URL.
The Google Search Console’s URL Inspection Tool proves invaluable in troubleshooting a page’s indexing status. It indicates whether a page is currently indexed and if it’s deemed indexable. In cases where indexability is an issue, the tool provides insights into potential reasons hindering Google’s indexing process.
Additionally, the URL offers insights into the last crawl date, indicating Google’s recent interest or activity concerning the page.
Conversely, Googlebot might opt for less frequent crawls if a page doesn’t undergo frequent changes. This approach aligns with conserving resources at Google and on the respective web server, a sensible optimization.
Moreover, the URL inspection tool allows users to initiate a crawl request when necessary.
2. Identifying Duplicate Content and Canonical Pages
Google’s subsequent recommendation involves examining whether a page is duplicated or if another page is designated as canonical.
According to the guidance, it’s typically acceptable if another page is established as canonical. The rationale behind this suggestion is explained as follows: “After crawling, the subsequent check involves verifying if it’s disregarded as a duplicate, with the canonical URL directed to another page. In most cases, this scenario is acceptable.”
Even if the canonical URL differs from what was expected, the content remains indexed and has the potential to appear in search results, making this situation generally acceptable.
Bonus Tip: Google advises against relying on the cache or site: search operator for diagnostic purposes. It might not appear in a site search even when indexing a page.
Like all other site operators, the site search operator operates independently of the search index. This has consistently been the case, even during the existence of a site search operator for displaying backlinks. Google emphasizes: “Avoid using cache or site search operators for debugging purposes as they aren’t designed for such tasks and might yield misleading results.
3. Verifying Rendered HTML for Irregularities
The final tip holds significant value. Google recommends distinguishing between examining HTML via the source code and inspecting the rendered HTML.
The term “rendered” denotes the HTML generated for browsers or Googlebot to display the webpage. When investigating potential HTML issues, scrutinizing the rendered HTML proves beneficial as it unveils what the browser and Googlebot perceive at the code level. Notably, the distinction between source code HTML and rendered HTML lies in the latter, revealing the HTML appearance after executing all JavaScript.
Consequently, reviewing the rendered HTML is pivotal for detecting issues linked to JavaScript or other elements that might remain unnoticed.
Google advises:
“…inspect the rendered HTML and the HTTP response for any unexpected elements.
For instance, an isolated error message or absent content due to technical glitches on your server or your application code.”
Explore Rendered HTML Using Search Console
Google Support offers a simple guide for accessing rendered HTML via the Search Console:
“Inspect the URL by either directly entering the URL into the URL Inspection tool or clicking on an inspection link adjacent to a URL displayed in most Search Console reports.
Proceed to Test live URL > View tested page.
The HTML tab displays the rendered HTML for the respective page.
View Rendered HTML Using Chrome DevTools
Utilize Chrome DevTools available in your Chrome browser to access the rendered HTML.
Access Chrome DevTools by navigating through the vertical ellipsis (three dots) dropdown menu:
More tools > Developer tools
For MacOS, press Command+Shift+P, and Windows/Linux/ChromeOS, press Control+Shift+P to open the Command Menu.
Enter “Rendering” in the Command Menu and select “Show Rendering” from the options.
Once selected, Chrome DevTools will display the rendered HTML in the lower window. You can easily interact with it using the mouse cursor, as illustrated in the screenshot below, allowing you to enlarge or manipulate the view as needed.
If you still need clarification, consider exploring our monthly SEO packages. Our experts are ready to lend a hand and guide you through the process.
