Publish machine-readable metadata for a site

Search engines read two things a human never sees: structured data that describes the page, and a sitemap that lists what exists. Getting both right is a small, unglamorous task with an outsized effect when something is wrong, because a malformed block is ignored and a sitemap that disobeys the protocol is quietly dropped. This job covers the pair in the order they matter. Describe the page first, then confirm the crawl surface tells the same story. The tools generate from the values you type and never contact your site, so no staging address or unpublished page is exposed while you work. Treat every generated fragment as a starting point to review, not a guarantee: nothing here promises a ranking, and a valid sitemap is still only a hint. Work one page at a time and verify as you go, because metadata faults are cheap to fix alone and expensive to untangle in a batch. Choose a type that matches what the page really is, then keep every declared field true to the visible content: a rating, a price or an author that appears nowhere on the page is a liability rather than an optimisation. Escape values so a quotation mark or an angle bracket cannot break the block. For the crawl surface, check that the sitemap lists only addresses that return successfully, that no staging hostname leaked into the markup, and that duplicate entries are removed, since repetition wastes the file's budget. Repeat the routine after a redesign rather than assuming old tags still describe the page. Two failure modes deserve a mention. The first is drift, where a page is rewritten but its description is not, so the snippet sells something the page no longer offers. The second is duplication, where several pages declare the same address and a crawler must guess which one counts. Neither is dramatic, and both are easy to catch in a routine pass. Keep a short note of the address and the tags you shipped, review them whenever the content changes, and treat the sitemap as a living index rather than a file written once. A checklist that names the person responsible for each tag keeps the habit alive long after launch week ends.