4 pages share the same meta description template after entity masking.
Write a unique meta description for each page that highlights what makes it specifically different.
2 ship-blockers, 1 should-fix
Heuristic score over 22 sampled pages, not Google's classifier. How to read this ↓
These rules still ran and emitted findings: the site-type profile lowered their severity so the score reflects how the signal applies to this kind of site, not a one-size-fits-all penalty.
aeo/answer-firstaeo/citable-factsaeo/freshness-signalscontent/missing-authorspam/thin-contenttech/og-completenessSave this audit to your history, sign in.
Monitor this domain with Pro →Your origin handled the crawl cleanly. Under Googlebot / AI-crawler bursts you should be fine.
content/meta-uniquenesserrormoderate6 pages4 pages share the same meta description template after entity masking.
aeo/llms-txtwarningmoderate1 pagesNo llms.txt found at https://ministryofpucks.com/llms.txt. llms.txt is a draft standard with low adoption: absence isn't a defect, only a missed opportunity.
4 pages share the same meta description template after entity masking.
Write a unique meta description for each page that highlights what makes it specifically different.
No llms.txt found at https://ministryofpucks.com/llms.txt. llms.txt is a draft standard with low adoption: absence isn't a defect, only a missed opportunity.
Create https://ministryofpucks.com/llms.txt to guide AI engines toward your most authoritative, citable content. Start with an # H1 title, a blockquote summary, then ## sections listing your key pages as markdown links. See https://llmstxt.org for the emerging convention.
https://ministryofpucks.com/ has no dateModified signal (no JSON-LD dateModified, no modification meta tag, no visible "Last updated"). Evergreen pages may legitimately omit this: verify whether freshness signals matter for this page type.
↗ ministryofpucks.com/Add a freshness signal so AI engines know the page is current. Three recommended places: (1) dateModified in your JSON-LD schema, (2) a visible "Last updated: YYYY-MM-DD" line in the page content, (3) accurate <lastmod> in your sitemap. For pSEO templates, automate dateModified to update when your underlying data source changes.
https://ministryofpucks.com/ has 0 unique citable facts. AI Overviews cite specific numbers and named references.
↗ ministryofpucks.com/Replace vague language ("varies", "several weeks", "affordable", "many options") with specific values a reader or AI engine would cite: exact prices, percentages, dates, timeframes, version numbers, named products, standards, or regulations that apply to this page. For pSEO templates, bind these values from your data source so each page gets entity-specific numbers instead of repeating the same template wording. Target: 8+ unique facts per page.
https://ministryofpucks.com/ has no author signals. This is an E-E-A-T risk. Author bylines matter most on blog/news content; technical docs and product pages legitimately omit them.
↗ ministryofpucks.com/Add author attribution: <meta name="author" content="Name">, a visible byline, or author data in your JSON-LD schema.
https://ministryofpucks.com/ is missing Open Graph tags: og:image.
↗ ministryofpucks.com/Add the missing meta tags inside <head>: <meta property="og:image" content="...">.
https://ministryofpucks.com/reservation has thin content (213 words). Some pages (landing pages, contact, status, tools) are legitimately short; verify whether this URL is meant to host substantive content.
Add at least 87 more words of substantive content relevant to this page's specific topic.
https://ministryofpucks.com/reservation does not open with a direct, extractable answer: no specific numbers, dates, or dollar amounts
↗ ministryofpucks.com/reservationRestructure the template to open with entity-specific facts. Instead of boilerplate or a topic preamble, lead with a complete-answer sentence containing the key number, date, agency, or form name a reader (or AI Overview) would cite. Target: <100 words, at least one concrete number, at least one named entity.
All 22 pages have fewer than 2 out of 4 E-E-A-T signal categories. Site-wide trust signals are missing.
Add trust signals site-wide: author info, publication dates, about page links, sources, or "last updated" markers.
https://ministryofpucks.com/blog/actualites/longueur-shuffleboard reads as FAQ content (2 question-style headings (e.g. "🥌 Plus c'est long, plus c'est bon ?", "🚛 Pourquoi les tables de compétition font 20,8 pieds ?")) but carries no machine-readable question/answer pairs.
↗ ministryofpucks.com/blog/actualites/longueur-shuffleboardFix this in the visible page, not in markup: give each question its own heading and put the complete answer in the first paragraph directly beneath it, so an answer engine can lift a whole question/answer pair without reassembling it. Do NOT add FAQPage JSON-LD expecting a rich result: Google removed the FAQ rich result from Search on 2026-05-07 and deleted its documentation on 2026-06-15, and QAPage is documented as being only for pages where users can submit answers, not for a site's own FAQ. If a non-Google consumer of your schema needs the markup, generate it from the same per-record data that renders the headings: don't ship identical questions with only the entity name swapped.
Is this your site?
Claim it to manage the listing, get a verified badge, and a followed backlink.
ministryofpucks.com passed the audit. Embed the badge on your site or README; it always shows your current grade.
[](https://pseolint.dev/r/kVigEfmBiW)<a href="https://pseolint.dev/r/kVigEfmBiW"><img src="https://pseolint.dev/api/badge/ministryofpucks.com" alt="pseolint grade for ministryofpucks.com" /></a>sitemap.xml as the source of truth. Pro lifts the budget to 500 pages on manual re-audits and crawls beyond the sitemap.