Examples — not case studies
Example work tickets
These are representative tickets for the kind of work a founding operator would queue. They are examples, not client results. No names, logos, traffic, or ROI.
Example
Mobile click-to-call
Observed trigger: The homepage shows a phone number as plain text, so a phone cannot tap it.
Bounded action: Add one visible tel: control using the approved number already on the page.
Verification: On a phone, the control opens the dialer with that same number. Nothing else is changed.
Example
City and service pages
Observed trigger: The homepage names a service, but the matching city or service page is missing or hard to reach.
Bounded action: Add or repair one city/service page from approved business facts only.
Verification: The page is reachable, states the service and area, and the primary action works.
Example
LocalBusiness schema cleanup
Observed trigger: Homepage JSON-LD is missing, uses the wrong type, or disagrees with the visible NAP.
Bounded action: Publish one LocalBusiness record from the approved name, phone, and locality.
Verification: Rendered structured data matches the public page. No extra locations are invented.
Example
GBP / NAP consistency
Observed trigger: The homepage name, phone, or locality does not match the Google Business Profile the owner provides.
Bounded action: Align the site NAP to the approved listing, or flag the conflict and stop.
Verification: Homepage, schema, and the provided listing use the same name, phone, and locality.