Report an Issue

Useful issue reports include page errors, broken internal links, incorrect titles or descriptions, sitemap failures, or obvious content mismatches on a route.

Reports tied to a precise URL are easier to investigate than broad statements about the site.

Include the exact page address, what was expected, what actually happened, and any visible error digest or server-side message. This structure reduces ambiguity during triage.

If the issue affects search or crawling, mention whether it was seen on a sitemap, category page, app page, or another indexable route.

Reported issues are prioritized by impact on availability, indexing, and user navigation. Server errors and crawl-breaking defects are typically the highest priority.

Content-quality reports may also lead to metadata updates, stronger explanatory text, or route-level schema corrections.