Thirty plus page data tags.
Applied automatically. Validated daily.

The full set covers every common content type a real site ships. Article, FAQ, and How To for content marketing. Product, Brand, and Review for commerce. Author, Organization, and LocalBusiness for entity signals. Event for conferences and webinars. Recipe for food sites. Video for embedded media. Breadcrumbs for navigation hierarchy. Plus JobPosting, Course, Book, Movie, Software, Dataset, ItemList, QAPage, and more. Thirty plus total, with new types added as the official specification grows.

Ranko reads the page, identifies what it actually carries, and picks the tag combination that signals that content correctly. A recipe with ingredients and a method gets Recipe plus Author plus Video if there is one, plus Breadcrumbs. A product page with price, specs, and reviews gets Product, Brand, Review, and Breadcrumbs. The decision is made from actual content rather than URL patterns, so the right tags apply even on customised pages. Most pages get four or five tags as a coherent set.

Whether every tag follows the structured data spec correctly and whether all required fields are present. For Recipe, the validator checks the recipe name, ingredients format, and cook time. For Product, it checks the product name, offer details, and brand reference. It catches malformed markup, missing required fields, and type mismatches. Using Google's own validator means it matches what Google will accept later.

The daily re check catches the break and routes it into the morning Site Inspector report with a one click fix ticket. The report shows the affected pages, what specifically broke, and the recommended fix. The corrected markup is included as copy paste ready content, so the developer or editor ships the repair without re-reading the structured data specification. Most broken tag issues get fixed the same morning they are caught.

Yes, the team can adjust the tag combination on any specific page if the default doesn't match their intent. The override interface shows the current tags, lets the team add or remove specific types, and re runs Google's validator on the new combination before saving. The override is per page and persists through daily re checks. The team always has the final call.

The same flow applies. Ranko reads the existing page, picks the right tag combination, validates against Google's checker, and applies the tags through the connection to the team's content management system. Pages from Article Writer get tags at write time. Pages from Page Refresher get tags updated during refresh. Existing pages get audited during the initial site crawl, and missing tag sets get queued for batch application that the team approves.