A passing Rich Results Test confirms that Google can read your markup. It does not confirm that Google will display it. Rich results depend on eligibility rules, indexing, rendering, page quality, and whether the markup matches what visitors see, and they disappear when Google retires a feature, as it did with HowTo in 2023 and FAQ on 7 May 2026. Conflicting plugin schema and review markup that breaks policy are two more frequent causes. UAE sites add AED pricing and Arabic and English page versions. As an SEO Agency in Dubai, infiniX360 audits these causes in a set order, from indexing through to feature eligibility. The sections below explain each cause, show how we diagnose it, and answer the questions clients ask most often.
A valid test result confirms syntax, not eligibility
The Rich Results Test and the Schema Markup Validator check whether your JSON-LD parses and whether required properties are present. Neither tool decides what Google shows. That decision comes from Google’s search systems, which weigh the query, the device, the quality of the page, and the reputation of the site. Google’s documentation states that markup does not guarantee a rich result. A product page with flawless markup can appear with price and availability for one query and as a plain blue link for another.
Indexing and rendering come before schema
Markup on a page that Google has not indexed produces nothing. We find noindex tags carried over from a staging site, canonical tags pointing to a different URL, and robots.txt rules that block the folder holding product or service pages.
Rendering causes a second group of failures. Googlebot can queue rendering behind crawling, so a page whose JSON-LD is injected by JavaScript or a tag manager may pass a live test while the indexed version still lacks the markup. Open the crawled page in URL Inspection and confirm that the structured data appears in the rendered HTML Google has indexed.
Markup has to match visible content and follow policy
Google requires structured data to describe content that users can see. Each mismatch below passes validation while disqualifying the page:
- Product markup lists one price in AED while the visible page shows a different promotional price after a script runs.
- A service page carries AggregateRating markup for the business itself, and Google’s review snippet guidelines do not allow self-serving reviews on LocalBusiness or Organization pages to earn star ratings.
- Availability is marked InStock while the visible button reads “enquire for availability”.
- Review markup names reviewers who appear nowhere on the page.
Misleading markup can also trigger a manual action, which Search Console lists under Manual actions. Affected pages lose rich result eligibility until Google reviews a reconsideration request.
Google has retired or restricted several result types
Some valid markup has no feature left to trigger. Google removed HowTo rich results in 2023 and limited FAQ results that year to well-known government and health sites. FAQ rich results stopped appearing in Google Search altogether on 7 May 2026, and Google scheduled the removal of FAQ reporting and Rich Results Test support for June 2026. In 2025 it also retired seven further features, among them Course Info, Estimated Salary and Vehicle Listing.
Google states that leaving this markup in place causes no harm. You can keep it for other systems that read it, but you should drop it from any rich result reporting.
Conflicting schema from plugins and themes
Many sites emit schema from the theme, an SEO plugin, and a page builder or review plugin at the same time. The output can include two Organization entities with different names or two Product blocks with different prices. Validators report each block as valid because each block is valid on its own. Conflicting values give Google no reliable basis for display, so we choose one source of schema for each type and disable the rest.
What UAE websites need to check
Sites in Dubai, Abu Dhabi and Sharjah carry a few extra variables. Product and Offer markup must declare AED as the price currency and match the price a visitor sees, with VAT shown the same way in both places. Arabic and English versions of a page need markup in the matching language, connected with hreflang, because a marked-up name that differs from the visible Arabic heading counts as a content mismatch. LocalBusiness markup should state your address, hours and phone number accurately, yet local pack placement still depends on your Google Business Profile.
How we diagnose the gap
We work through six checks in order, because each one can make the next irrelevant.
|
Check |
What we look for |
Where we look |
| Indexing | Noindex tags, canonical conflicts, blocked paths | URL Inspection, Page indexing report |
| Rendering | Markup in the rendered HTML of the indexed page | URL Inspection, crawled page view |
| Content match | Prices, ratings and availability that differ from the visible page | Page source against the live page |
| Policy | Self-serving reviews, hidden content, manual actions | Search Console, Manual actions |
| Eligibility | Feature still supported for your page type | Google Search gallery |
| Monitoring | Impressions by search appearance after each fix | Performance report, Search appearance filter |
We have worked with 500+ clients across 50+ industries over 13+ years, and we document every task with screenshots so you can verify each fix on your own site.
Conclusion
Valid structured data is the entry requirement for a rich result, and it does not decide the outcome. When enhancements fail to appear, the cause usually sits in indexing, rendering, a mismatch with visible content, a retired feature, or markup that two plugins emit with different values. Working through them in that order separates a markup problem from a feature or quality limit. If you run a site in the UAE and want this review applied to your own templates, our team provides SEO Services in Abu Dhabi, Dubai and Sharjah.
Frequently asked questions
Does passing the Rich Results Test guarantee a rich result?
No. The test confirms that your markup parses and meets the technical requirements for a feature. Google then applies its own eligibility, quality and relevance checks for each query, so a valid page can still appear as a standard listing.
How long does Google take to show rich results after a fix?
Google must recrawl the page, reprocess the markup, and then decide whether to display it. Request indexing in URL Inspection after the fix, then watch the Search appearance filter in the Performance report over the following weeks.
Can valid structured data that produces no rich result harm my rankings?
Google has stated that unused structured data does not cause problems for Search. Misleading markup is different, because it can lead to a manual action that removes rich result eligibility for the affected pages.
Should I remove my FAQ schema now that FAQ rich results are gone?
Removal is optional, since Google confirmed the markup can stay without harming performance. Keep it only where the questions and answers appear on the page for visitors, and stop expecting FAQ boxes in Google results.
Does structured data help a page appear in AI Overviews?
Google states that AI Overviews and AI Mode have no additional technical requirements and no special schema. It does list matching structured data to the visible text among the fundamentals that remain worthwhile, so accurate markup helps without being required.
Which rich results are still worth pursuing?
Check Google’s Search gallery before you build, because supported types change. Product snippets, merchant listings, review snippets, events and breadcrumbs remain documented, and each has eligibility rules and policy limits that your content has to meet.