honing_services
slug: honing-services · round 5 Approved
Signed off by zachbenzbf@gmail.com 41d ago ·
4 rounds of feedback before approval
Compliance review
✓ Approved — daemon is applying / has applied generated 2026-05-21T03:34:39Z
Auto-fixes already applied (10)
contact_consent · 3
- pages/inquiries.astro: rewrote consent to drop unsupported 'accredited' adjective (CREDENTIALS CLAIMED is empty), aligned contact methods to 'phone or email', kept business + service providers, kept TCPA 'Consent is not required to receive a quote', kept Privacy + Terms links.
- pages/[hub]/[service].astro: same consent rewrite as inquiries.astro (dropped 'accredited', aligned to 'phone or email').
- components/SplitForm.astro: consent text was previously missing service providers, TCPA disclosure, and Terms link. Rewrote consent to cover all required elements: BOTH business and its service providers, 'phone or email' methods, scope 'this service request', 'Consent is not required to receive a quote', links to BOTH Privacy Statement AND Terms of Engagement. Added termsHref prop to support the second link.
form_endpoints · 2
- components/SplitForm.astro: default formAction changed from '/api/inquiry' to '/api/submit' (matches forms_setup canonical endpoint).
- pages/index.astro: SplitForm formAction prop changed from '/${contactSlug}/' (i.e. '/inquiries/' — incorrect, would have routed the homepage form to the contact page instead of the lead handler) to '/api/submit'. Also added the new termsHref prop so the SplitForm consent renders both legal links.
blog_index · 2
- pages/blog/index.astro: rewrote lede 'Insights, guides, and notes from the team.' → 'Industry articles, technical references, and procedural guidance.' (passive, no 'the team' provider reference).
- pages/blog/index.astro: added noindex={true} to BaseLayout (blog system is BETA per project memory; indexing an empty archive hurts SEO).
spun_content · 3
- service-geo-content/plateau-honing-services/aurora.html: 'We provide coverage for industrial sites across Aurora…' → 'Coverage extends across Aurora…' (passive).
- service-geo-content/gear-honing-services/racine.html: 'We provide coverage across Racine…' → 'Coverage extends across Racine…' (passive).
- Smart-quote / em-dash / en-dash ASCII normalization applied to 29 spun fragments: block-honing-services/michigan.html, block-honing-services/green-bay.html, engine-block-honing-services/milwaukee.html, plateau-honing-services/milwaukee.html, plateau-honing-services/green-bay.html, cylinder-honing-services/evansville.html, cylinder-honing-services/elgin.html, cylinder-honing-services/indianapolis.html, keyway-honing-services/schaumburg.html, keyway-honing-services/indianapolis.html, horizontal-honing-services/green-bay.html, horizontal-honing-services/kenosha.html, vertical-honing-services/appleton.html, vertical-honing-services/hammond.html, vertical-honing-services/milwaukee.html, bore-honing-services/schaumburg.html, bore-honing-services/chicago.html, bore-honing-services/evansville.html, gear-honing-services/appleton.html, hydraulic-cylinder-honing-services/schaumburg.html, hydraulic-cylinder-honing-services/michigan.html, hydraulic-cylinder-honing-services/chicago.html, flat-surface-honing-services/wisconsin.html, tube-pipe-honing-services/illinois.html, tube-pipe-honing-services/kalamazoo.html, tube-pipe-honing-services/racine.html, mold-honing-services/wisconsin.html, form-honing-services/milwaukee.html, form-honing-services/waukesha.html (em-dash → --, en-dash → -, smart quotes → ASCII).
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-05-21T13:59:58.431482Z
Auto-fixes already applied (1)
items · 1
[
{
"file": "src/pages/inquiries.astro",
"pattern_matched": "Inquiries are reviewed and routed by [criteria] (D2 routing/directory mechanism tell)",
"before": "Inquiries are reviewed and routed by part type, geometry, and location.",
"after": "Inquiries are reviewed by part type, geometry, and location.",
"location_hint": "Section 'After you submit' (DOC REF: CON-01), first paragraph in the prose block"
}
] 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 232 service pages
- sample hub sample · fix applies to all 29 hub pages
- capabilities single page
- contact / quote form single page
Round history
Round 1 · 43d ago · 1 issue
- There is an issue in the mobile version where the width is not correct I go to the URL and I have to zoom out and the image is not fitting the width of the screen so that issue needs to be fixed also the text under the hero image the little codes and numbers and stuff is kind of running over the image in that part you can't really see so we got to fix the visibility of that part also on the service pages and on the home pages there is some content that violated the accordion rule and needs to get folded up into accordions kind of like that SEO content that's found in the service pages and whatnot so let's try to fix all of these things on the first passover
Round 2 · 43d ago · 1 issue
- I have attached the image that displays the issue on mobile that sidebar needs to be fixed and it needs to be displaying properly so that's what it looks like. I think it may be an issue with the nav bar because the nav bar needs extra space over there because the navbar pops out so maybe it's related to the nav bar.
Round 3 · 43d ago · 1 issue
- Get rid of the service coverage map because it's not displaying properly so just get rid of it completely. Also for mobile the name of the company on the nav bar is truncated so let's just make it say Chicago honing instead of Chicago precision honing so it can all display there. And also the H1 is good but I almost want the H1 to appear as though it's not the H1 because we just want the SEO value from that keyword being there and we want the H1 to actually appear as though it says Chicago honing so the larger text would say Chicago precision honing and above it in the little text it might say honing services Chicago and that technically will be the H1 but the styling will make it look like it's not.
Round 4 · 41d ago · 1 issue
- Treat this niche as a SHIP-TO-LOCATION business — customers ship their parts to our central facility for honing; we do NOT travel to the customer's location. Therefore the site must NEVER say "[Service] in [City]" or "[Service] in [State]" anywhere — H1s, meta titles, hero copy, body paragraphs, section intros, CTA labels, image alt text. Saying "in [City]" implies physical presence in that city which we don't have and reads as deceptive. Replace EVERY 'in [City]' / 'in [State]' pattern site-wide using these rules (pick the natural one per context): - H1s + meta titles: bare adjacency. "Engine Cylinder Honing in Chicago" -> "Engine Cylinder Honing Chicago". Same for state names ("in Illinois" -> "Illinois"). Same for every service × city/state combination. - Sentences/body copy: "for [City]" or "serving [City]" or "[City]-area" reads more natural. E.g. "honing services in Chicago" -> "honing services for Chicago" or "Chicago-area honing services". - Template literals like `${service.name} in ${city.name}` -> `${service.name} ${city.name}` (drop the 'in '). - schema1.business.service_area_business is now FALSE so any template that conditionally renders 'in' based on that flag is fine left alone (the condition handles it). Use Playwright to navigate to https://honing-services.pages.dev/, spot-check 2-3 hub pages (e.g. /chicago/, /milwaukee/) and 2-3 service pages (e.g. /chicago/engine-cylinder-honing-services/) BEFORE editing, to identify where 'in [City/State]' appears. Then grep the entire src/ tree for 'in {city.name}' / 'in {state.name}' / hardcoded 'in Chicago' / 'in Illinois' / etc. and rewrite all of them. JSON-LD structured data (PostalAddress.addressLocality, etc.) is FINE as-is — only visible text needs the change. The footer NAP literal string (e.g. '2924 E 126th Pl, Chicago, IL') is also fine — that's the actual mailing address, not an in-City service claim. After your edits, re-navigate via Playwright and confirm 'in Chicago' / 'in Illinois' / etc are absent from the visible text on the same spot-checked pages.
✗ Link gap: Skipped
decided 2026-05-24T01:57:39.333Z
✗ Blog: Skipped
decided 2026-05-24T01:57:44.493Z