pressure_calibration
slug: pressure-calibration · round 4 Approved
Signed off by zachbenzbf@gmail.com 18d ago ·
3 rounds of feedback before approval
Compliance review
✓ Approved — daemon is applying / has applied generated 2026-05-29T19:59:57Z
Auto-fixes already applied (14)
terms · 1
- No changes required — terms.astro already contains all required TOS concepts: coordination-platform (not direct provider) description (§1), work performed by independent accredited providers (§2), provider selection/vetting + no-warranty + AS-IS (§3), quotes/service-agreement disclaimer (§4), customer responsibilities (§5), industry/compliance disclaimers (§6), limitation of liability (§7), indemnification (§8), and noindex via BaseLayout (noindex={true}).
privacy · 1
- No changes required — privacy.astro already contains all required concepts: data collected incl. form fields + communications + technical logs (§2), shared with providers and explicitly not sold for marketing (§4), data retention (§6), rights to access/correct/delete (§8), CCPA/CPRA (§9), other state privacy laws (§10), children's privacy (§11), and noindex via BaseLayout (noindex={true}).
contact_consent · 3
- components/QuoteForm.astro (live on homepage via index.astro) — form had NO consent checkbox at all. Added a TCPA-compliant consent field (input name="consent", required): authorizes {businessName} AND its independent accredited providers, contact by phone and email, scoped to 'this service request only', includes 'consent is not required to receive a quote', and links to both the Privacy Policy and Terms of Service. Added businessName/privacyUrl/termsUrl bindings in frontmatter to support it.
- pages/request-a-quote.astro — already compliant (business + providers, phone and email, this service request only, consent-not-required, Privacy + Terms links). No change.
- components/HeroLead.astro (used by [hub].astro and [hub]/[service].astro) — already compliant. No change.
form_endpoints · 4
- components/QuoteForm.astro — rewrote form action from `/${contactSlug}/` (an early-template draft pointing at the contact-page slug) to action="/api/submit"; normalized method to POST and removed the now-unused contactSlug binding.
- components/HeroLead.astro — already action="/api/submit". No change.
- pages/request-a-quote.astro — already action="/api/submit". No change.
- components/ServiceCoverage.astro — contains a ZIP/city coverage-lookup form (no lead capture, no consent); out of scope, left unchanged.
blog_index · 2
- pages/blog/index.astro — rewrote hero lede 'Insights, guides, and notes from the team.' -> 'Industry articles, technical references, and procedural guidance.' (removed 'the team' provider language).
- pages/blog/index.astro — added noindex={true} to BaseLayout (BETA blog / empty archive should not be indexed).
spun_content · 3
- service-geo-content/accredited-industrial-pressure-gauge-calibration-services/flint.html — rewrote first-person service-delivery sentence 'We maintain comprehensive calibration coverage across these key industrial corridors, bringing metrology solutions directly to regional manufacturers, utility providers, and testing laboratories.' to passive: 'Comprehensive calibration coverage extends across these key industrial corridors, with metrology services available to regional manufacturers, utility providers, and testing laboratories.'
- Replaced em-dash/en-dash/smart-quote characters with ASCII (--, -, ', ") in 11 fragments: service-geo-content/accredited-industrial-vacuum-gauge-calibration-services/saint-louis.html; .../pressure-switch-relief-valve-calibration-services/illinois.html; .../pressure-switch-relief-valve-calibration-services/hopkinsville.html; .../vacuum-gauge-calibration-services/fishers.html; .../pressure-gauge-calibration-services/saint-louis.html; .../leak-tester-calibration-services/minnesota.html; .../leak-tester-calibration-services/aurora.html; .../vacuum-gauge-calibration-services/rockford.html; .../piston-gauge-calibration-services/milwaukee.html; .../pressure-transmitter-transducer-sensor-calibration-services/lexington.html; .../leak-tester-calibration-services/south-bend.html.
- Voice scan of all 640 service-geo-content fragments found NO superlatives (industry-leading/world-class/etc.), NO banned CTAs (free quote/call today/etc.), NO directory-marketplace tells referring to the site, and NO misapplied 'NIST-traceable' usage (all 631 NIST references correctly describe reference standards, certificates, or measurement data).
Decisions submitted — daemon is/has applying
Orchestrator syncs R2→local within 60s. Daemon then runs the apply
step (Claude+Edit) and continues. Live progress on the niche detail.
Voice audit review
✓ Approved — daemon is applying / has applied generated 2026-06-14T19:23:45.179484+00:00
Decisions submitted — daemon is/has applying
Orchestrator syncs R2→local within 60s. Daemon then runs the apply
step (Claude+Edit) and continues. Live progress on the niche detail.
Pages to review (5)
These are the exact pages the auto-QA agents inspected. Open each, look it over, and use the feedback box below to list anything wrong. Hub and service entries are samples — feedback about them propagates to every hub or service page in the niche at build time (you don't need to mention each one individually).
- homepage single page
- sample service page sample · fix applies to all 640 service pages
- sample hub sample · fix applies to all 64 hub pages
- capabilities single page
- contact / quote form single page
Round history
Round 1 · 19d ago · 2 issues
- One issue is the logo on the nav bar, it is a bullshit logo we need something that looks like a real logo. Also the exact same verbage is used leading off every single service panel on the homepage and it reads slightly repetitive and robotic
- On geo-landing-page homepages the H1 keyword needs to STAY as the service keyword for SEO (e.g. 'Industrial Pressure Calibration'), but it currently reads as the giant visible page header, which feels awkward/templated. Format the H1 small/de-emphasized (treat it as semantic SEO markup, not the visual headline), and promote a different element — like a short paragraph/lede or a stylized brand line — to be the visually prominent header instead. The SEO value stays, the page feels designed.
Round 2 · 19d ago · 5 issues
- you added lead gen terminology. unacceptable. no "intake and scheduling" or "coordinating" language. remove it.
- CRITICAL: the round 1 H1 fix is STILL NOT IMPLEMENTED. The H1 must remain the service keyword (e.g. 'Industrial Pressure Calibration' or whatever the SEO target is) — semantic <h1> tag, kept for SEO — but VISUALLY render it small/de-emphasized (smaller font, less weight, treat as a kicker or label, NOT the giant page header). The visually prominent header on the homepage should be a DIFFERENT element: the brand name 'Premier Pressure and Gauge Calibration' rendered large, OR a short designed lede paragraph. Do NOT replace the H1 with marketing copy. Do NOT add 'intake/scheduling/coordinating' language anywhere. Just restructure the CSS so the existing semantic H1 is visually small.
- The brand/business name has been changed to 'Premier Pressure and Gauge Calibration'. Update every user-visible reference (header logo text, footer, about copy, schema.org JSON-LD, meta tags) to use this name. Do NOT change the H1 service keyword.
- ADDITIONAL ROUND 2 FEEDBACK (user, must address): 1. The favicon (the small logo shown on the BROWSER TAB) is still the old/default. It needs to match the NEW nav-bar logo. Generate/copy the new logo into the favicon slot (favicon.ico + apple-touch-icon + the Open Graph image used by social/SERP image-card surfaces). The favicon/tab icon must visually match the new nav logo, not be a fallback letter mark. 2. SERP result currently shows the URL repeated twice instead of the BRAND NAME. The site needs to surface the brand 'Premier Pressure and Gauge Calibration' to Google as the canonical site name. Required fixes: - <title> tag must lead with the brand or include it (BaseLayout + page meta_title) - WebSite JSON-LD must set "name": "Premier Pressure and Gauge Calibration" - Organization JSON-LD must set "name": "Premier Pressure and Gauge Calibration" - og:site_name meta tag must be "Premier Pressure and Gauge Calibration" - Apex domain Pages config (and any sitelinks search box) must not let Google fall back to the URL. USER NOTE: this has been asked multiple times. No skipping. Verify by checking the deployed page source has all 4 surfaces (title, WebSite JSON-LD name, Organization JSON-LD name, og:site_name) explicitly populated with the brand name. 3. The new nav-bar logo is GOOD — keep it. Whatever generation path produced it on this round, that pattern needs to become the default for all future niches. Capture the recipe (model/prompt/style/seed/post-processing) so cmm_calibration / temperature_calibration / lapping_services / honing_services / polishing_services can be retroactively regenerated to this same quality level.
- 4. The "Our Process" page (which serves as the de-facto About page in our pipeline) is THIN and doesn't feel like a real brand. Needs: - Substantive content that demonstrates EEAT (Experience, Expertise, Authoritativeness, Trustworthiness) without making things up. Reference real industry standards (ISO/IEC 17025, NIST traceability, ANSI/NCSL Z540, manufacturer-specific tolerances) where genuinely applicable. Cite specific instrument classes the providers calibrate. Reference what the certificate of calibration actually contains (as-found / as-left readings, measurement uncertainty, traceability chain) — that's all real and verifiable. - Use passive voice for service delivery ('calibration is performed by ISO/IEC 17025-accredited laboratories'), active voice OK for brand actions ('we coordinate provider matching'). - NO lead-gen terminology — no 'intake and scheduling', no 'coordinating with our network', no 'matched with the right shop', no 'connecting buyers with providers'. The page should read as the brand explaining ITS process for getting work done, not as a directory describing how it routes buyers. - Avoid 'platform' / 'marketplace' / 'directory' framing entirely. - DO NOT FABRICATE: no fake credentials, no made-up case studies, no fake testimonials, no claimed certifications the brand doesn't actually hold. Lean on the accredited LABORATORY partners' real credentials, which the brand coordinates with. - Should feel branded — typography pairing, real numbers/stats that are genuinely verifiable, photo arrangement that breaks from the templated grid, content depth >= 600 words of substantive copy not filler.
Round 3 · 19d ago · 2 issues
- Same identical-verbiage problem that was fixed on the homepage service cards now needs to be fixed on the CAPABILITIES page too. The service cards on /capabilities/ all lead off with the same boilerplate first sentence ("Calibration is performed across N [type] instrument types to recognized tolerances, with results documented for audit and traceability." or near-identical). Homepage was fixed but capabilities page has the same templated lede across every card.
- Fix: rewrite the lede on each service card on the capabilities page so each one has a UNIQUE opening sentence that's specific to that service. Same passive voice + no lead-gen vocab rules from prior rounds apply. Each card's first sentence should reflect the actual instrument class / measurement chain / what's distinct about THAT calibration work (e.g. pressure transmitter calibration mentions 4-20 mA loop verification; piston gauge mentions primary standard / cross-float; manometer mentions reference column; etc.). 600+ char content per card minimum, factually accurate, no fabrication.
✗ Link gap: Skipped
decided 2026-06-14T19:00:31.797Z
✗ Blog: Skipped
decided 2026-06-14T19:01:01.793Z