Verify the connection

The check runs when you click I added it. Check now on the Setup step, or Check now / Try again on the Check step. The app requests https://<your-domain>/work/_health from its own servers, so a browser-side block or cache does not affect it, and reports one of the outcomes below. The last result stays on the page if you come back later.

Any result other than success keeps the connection unfinished. Fix the cause and check again; you don’t need to re-paste unless a step below says so.

You’re connected.

Your project pages are live.

Done. The wizard moves on to the next setup step.

Almost there.

We reached your site, but the setup is pointing to a different business. Double-check the snippet matches the business you’re setting up here.

The rule reached SimplifyLocal with a different business ID in it. Copy the snippet again from this business’s Setup step (the ID is filled in there), replace the one on the host, redeploy or reload, and check again. This usually happens when an account has more than one business and the snippet was copied from the wrong one.

The setup hasn’t been added yet.

Re-check the snippet you pasted. Make sure you saved your changes after pasting (some hosts also need a redeploy).

/work/_health returned a 404 from the site itself. The rule isn’t in effect yet. Confirm:

• The file was saved and, on Netlify and Vercel, the deploy that includes it has finished.
• The rule covers both the bare /work path and /work/*. Each host page shows the two-part shape.
• On Cloudflare, the Worker route is on the right zone and matches yourbusiness.com/work/*.
• On Apache and Nginx, the server was reloaded.

We can’t reach your site.

This usually means DNS hasn’t caught up yet. Wait 5 minutes and try again.

The request timed out or the domain didn’t resolve. Wait and try again. If the site itself loads in a browser but this keeps happening, make sure the address in the Web address step is the one the site actually serves on.

Your site is forwarding to us, but not the way we expect.

The request is reaching us, but it arrives with your site’s own web address instead of ours. On Apache, remove any ProxyPreserveHost On line. On Nginx, remove any proxy_set_header Host line. On other hosts, remove the snippet, paste the current one from the previous step again, then check again.

The rule forwards to SimplifyLocal, but the request reaches proxy.simplifylocal.app carrying the site’s own host name, so it is treated as a direct hit rather than a proxied one. The snippets set no secret and no extra headers; the destination host is the whole signal. Apache’s default (ProxyPreserveHost Off) and Nginx’s default (no proxy_set_header Host) already send the right one, so only an added override needs removing. The /work locations in particular must not inherit a server-wide proxy_set_header Host $host.

Something on your host is returning an error.

Try again in a minute. If it keeps happening, email help@simplifylocal.app and we’ll dig into it with you.

The site answered with a server error or an unexpected response. Try again shortly. If it persists, email help@simplifylocal.app with the web address and the host.

After it passes

Two more steps make the pages findable: Link the pages from your site and Sitemap and robots.txt. Both live under Setup → Get found on Google.

Later on, Settings → Connections → Website links has a Test my web address button that re-checks the site, the /work path and the links between the pages and the rest of the site in one go.