Two addresses, one site
A Webflow project answers on its webflow.io address and, once a custom domain is connected, on the client’s domain. Both can be live at once. Webflow’s help centre describes a setting in the site settings (SEO, then Indexing) that stops search engines indexing the webflow.io subdomain, and says it needs a Site plan or a paid Workspace. That setting concerns the subdomain. Whatever the custom domain serves is a separate matter, so a project can have two addresses and two sets of robots rules, and both need a look.
Decide which address the client’s customers use, monitor that one as the site, and keep the other in mind. Beamfar records a page becoming noindex and a robots.txt that starts to block it on the address it checks. It does not report that a staging address is indexable, so look at the staging address’s source and robots.txt by hand after a launch. Google describes how to read a noindex rule in Block Search indexing with noindex.
What goes wrong on a Webflow site
A publish changes the search settings. Indexing and robots rules are set per project and take effect when the site is published. A switch that was right for the review copy can be carried to the live domain by the next publish. The page stays up, the traffic falls. The SEO guard alerts when the page becomes noindex or robots.txt starts to block it, after a second sighting.
The custom domain stops pointing at Webflow. Webflow’s instructions for a custom domain ask for two A records on the root name, a CNAME for www and a TXT record that proves ownership, with values shown in the site settings. They also say Webflow hosting does not support the Cloudflare proxy, so a client who turns on a proxy in front of the domain can break the site. Domains are changed by registrars, DNS providers and the client’s other agency. Write down the values Webflow shows when you launch, and let the DNS check compare them with what the name returns later. See DNS changes that break client websites.
A redirect list sends visitors to the wrong place. Redirect rules are kept with the project and are easy to extend by hand. A mistake produces a chain or a loop that a status-code check shows as a final address that changed. Beamfar records the final URL of the page check and flags a redirect that starts pointing somewhere new. See Redirect chains after a site migration.
A form stops reaching the client. Webflow forms submit to Webflow and notify an address you set. No outside monitor can fill in and read a form, and it should not send test submissions to a client’s inbox every minute. Put a form test in the monthly routine and write the notification address down.
The certificate and the domain. Webflow provides the certificate when SSL is on for the domain, and the registration still expires at the registrar. The certificate check and the domain expiry check run on every site. See Domain expiry and RDAP.
The checks that matter most
| Check | What it catches here | How to set it up in Beamfar |
|---|---|---|
| Page with required text | A page that answers but shows an error, a password or a published draft | The page check on the production address; require a phrase from the live footer |
| DNS records | The domain repointed, the root name or www changed | Automatic: A and AAAA records, with a change on the timeline |
| Search settings | noindex or a robots.txt block after a publish | Automatic: an alert after a second sighting |
| Redirects | A new final address after someone edited the redirect list | Automatic: the final address of the page check is recorded |
| Certificate and domain registration | Expiry and a name that does not match | Automatic on every site |
| Sitemap | A sitemap that disappeared or lost its pages, if the site publishes one | The sitemap monitor, within the limits of the plan |
Set it up
- Add the production host name in the portfolio. If the client uses
wwwand the root name, add the one they want people to see and keep the other as a redirect. - Require text from the live page. Use the footer, not a heading the client may reword.
- After launch, copy the DNS values from the site settings into the client’s care notes, then open the site’s timeline a week later to confirm nothing changed.
- Open
robots.txtand the page source of both addresses once, and note whether each is meant to be indexed. - Send the alert to the person who can reach the registrar and the DNS provider, not only to the person who designs the pages.
What an outside check cannot see on Webflow
It cannot see the Designer, a draft that was never published, the CMS entries, a form submission or a Workspace permission. It does not know that a page is slow because of an embedded script, though the response time and the crawl’s mixed-content list point to it. For the rest, keep a short launch and handover checklist in the care plan and read the multi-platform view in Monitoring Shopify, Webflow and WordPress sites from the outside.
How Beamfar helps
Beamfar is not a Webflow app and works the same on any host. It checks the public site from two regions, calls it down only when both agree, records DNS, certificate, redirect and search-setting changes on one timeline and alerts when the certificate or domain registration nears its end. It has been tried on test pages only and has no customers yet.
Questions
Do I need to install anything on a Webflow site to monitor it?
No. The monitor requests the public address from outside, the same way a visitor does.
Why is the webflow.io address still in Google?
The indexing setting for the subdomain only takes effect when the site is published, a plan requirement applies, and results already indexed can stay for a while. Check the address’s robots.txt and source after publishing.
Can I monitor a form on a Webflow site?
Not safely from outside. A monitor that submits forms would fill the client’s inbox. Test the form by hand in the monthly routine.
Which DNS records should I write down?
The ones Webflow shows in the site settings for the custom domain: the A records for the root name, the CNAME for www and the TXT record that proves ownership.
Sources
Read on . Standards and vendor pages change; confirm the current text before you rely on it.
- Webflow help, Disable search engine indexing (read through a search summary of the page, which refused an automated read) (help.webflow.com)
- Webflow help, Manually connect a custom domain (read through a search summary of the page) (help.webflow.com)
- Google Search Central, Block Search indexing with noindex (developers.google.com)