Content Quality
Part of JavaScript and search visibility
Checking whether rendered content includes the main page information
Define a page's essential answer, inspect its rendered HTML and record what is missing without treating a live test as proof of indexing.
Check whether Google’s rendered HTML contains the answer the page promises, including any condition that changes a reader’s decision. A heading or loading frame can appear even when the service details, product information or article text never arrive.
Define the expected answer
Choose one exact URL and list what someone needs there: the main heading, central explanation and important limits. On a service page, that might be the service offered, its coverage and how to enquire. Treat decoration separately from information needed to decide or act.
Inspect the rendered result
In a Search Console property you control, inspect the URL, run a live test and open the tested page’s HTML. Search for distinctive parts of the expected answer. Google’s Rich Results Test or the URL Inspection Tool in Search Console can also show rendered HTML for a URL.
Check the complete statement, not one matching word. Finding ‘delivery’ is insufficient if the page’s qualification ‘selected postcodes only’ is missing.
If media carries essential information, check its rendered element and usable URL. A screenshot can reveal a blank area or loading state, while the HTML shows which text and elements were present in that test.
Observation / Next check
- Main text is present
- Check that its qualifications and next action are also present.
- Only a loading state appears
- Inspect the content request, required scripts and JavaScript errors.
- Similar pages render correctly
- Compare the failing page's data and request path.
- Live and indexed views differ
- Record their dates; Google's indexed information may be older.
Live Test vs Indexed View: Key Differences
- Live Test ResultShows how Google crawls and renders the page at the time of testing
- Indexed View (in Search Console)May reflect an older version of the page; not always current
- When to Use EachUse live test for real-time rendering issues; use indexed view to check what’s currently in search results
State the narrow result
If the main answer is absent, investigate how that answer is delivered and retest the same URL after a change. If it is present, record that finding without treating it as proof of indexing. A live test shows how Google crawls and renders that URL; the Rich Results Test and the URL Inspection Tool in Search Console are provided for that purpose.
Keep the URL, expected information, test date and any missing qualification together. An ordinary browser view can help reproduce a problem, but it does not replace Google’s rendered result for this check.
