Forerun / Sample free presence check
New York City · Independent neighborhood restaurant
Easy to find. A few details make it harder to visit.
The business’s core details are consistent in this demonstration, but conflicting Sunday hours and a broken reservation link create avoidable friction. Fix those first, then address unanswered reviews and outdated profile content.
John Doe’s Restaurant is fictional. Every observation, count, score, and platform example below is invented to demonstrate the format of a free presence check—not the result of live research.
First priority
Give customers a working route to a table and a clear answer about when you’re open.
01 / What we checked
A free presence check reviews selected public-facing details and links. Coverage depends on the business; it is not a complete technical, legal, or account-access audit.
Google Search and Maps, Apple Maps, and Yelp: business identity, hours, website, and contact paths.
Website and reservation destination: can a customer reach a working booking page and current menu?
Visible review responses, profile imagery, and whether public content reflects the business.
Instagram bio and link destination. Other directories are reviewed only where relevant.
02 / Findings
Demo observation: Name, address, and phone number match across the website, Google, Apple Maps, and Yelp.
Why it matters: Customers get a consistent identity and contact route.
Recommendation: Preserve one owner-approved record and check it whenever business details change.
Demo observation: Google displays Sunday hours of 12–9 pm; the website displays 12–8 pm. These are the two conflicting schedules noted in the homepage preview.
Why it matters: A customer cannot confidently plan a late visit.
Recommendation: Confirm the correct hours with the owner, update affected profiles, and check holiday exceptions.
Evidence in a real check: dated screenshots, profile links, and owner confirmation. None are fabricated here.
Demo observation: The primary “Book a table” link leads to an error instead of a reservation page.
Why it matters: An interested diner reaches a dead end.
Recommendation: Replace the link with the owner-approved reservation destination and test it on mobile and desktop, including links from business profiles.
Evidence in a real check: originating page, destination URL, observed error, and test date.
Demo observation: Three recent reviews have no visible business response.
Why it matters: Feedback is an opportunity to answer questions and show attention.
Recommendation: Draft specific, thoughtful replies for owner approval. Report suspected fake or abusive reviews only when there is a policy-based reason; removal is not guaranteed.
Demo observation: A featured menu image shows a retired seasonal item, and the Instagram bio leads to an older menu page.
Why it matters: Guests may arrive with expectations the current menu cannot meet.
Recommendation: Confirm current offerings, update owner-managed images, and point the bio to a maintained menu or booking destination.
03 / Recommended next steps
Timing is illustrative and depends on owner approvals, platform access, and verification requirements. No changes are made as part of this sample.
How to read this sample
The 74/100 is an illustrative Forerun summary—not a Google score or a prediction of search placement, revenue, or AI recommendations. For this example, it comprises identity 20/20, hours 12/20, customer paths 10/20, reviews 16/20, and profile content 16/20. Equal weighting is used only to explain this demonstration.
A real free check would identify the profiles reviewed, record observed issues with supporting links or screenshots, distinguish confirmed facts from questions for the owner, and prioritize practical fixes. It would not include account changes, a full review-history analysis, or guaranteed outcomes.
Your business, next.
Email your business name and website or listing link. We’ll identify the first things to check.
Request your free check ↗No purchase required.