Most Plone sites grow for years. Along the way they accumulate accidental duplicates, orphaned pages, messy URLs and translation gaps. Editorial teams rarely see this clearly, because seeing it usually means paying for an external SEO tool or letting a third-party crawler loose on the site — often a non-starter for public bodies and universities with strict data policies. This talk introduces interaktiv.sitemapaudit, a Plone 6 add-on that takes a different route: instead of crawling, it reads the sitemap.xml.gz that Plone already publishes, parses every URL and its lastmod date, and turns that into an instant structural health check — no external calls, no data leaving your Plone. We walk through the control panel: headline metrics like URL count and path-depth distribution, translation coverage for multilingual sites, and five findings categories — copy_of duplicates, underscore URLs, overly long slugs, stale pages, and missing translations in both directions. A sortable table, context-sensitive filter chips and a spreadsheet-friendly CSV export turn the audit into an actual editorial to-do list, not just a report nobody reads. Expect a live demo on a real site. What you will take away: - A practical way to audit content structure without external SEO tools or crawlers, using only data Plone already exposes. - A concrete checklist of structural issues worth hunting down — duplicates, stale content, URL hygiene, translation gaps — and why each one matters editorially. - How to turn a technical audit into a workflow your content team will actually use. - Design patterns for privacy-first Plone add-ons that keep all data inside the customer's own system.