A Webflow Designer extension. Press one button and see what is still left over on your site — including inside your components, the part the built-in checks leave to you.
What it finds
The page setting “Exclude this page from site search results” is still on. That page will not appear in the search results on your own site.
On a single page, or on the whole site. Visitors cannot open it.
No destination set, or still pointing at #.
Nothing happens when someone clicks it.
“Lorem ipsum” and the rest of the filler. Text nobody meant to publish stays on the finished page.
A link still pointing at a .webflow.io address that is not this site.
It sends your visitors to something you are still working on.
Where it fits
| Checked for | The built-in checks | GoLive Check |
|---|---|---|
| Heading structure | ✓ | — |
| Image alt text | ✓ | — |
| Meta title and description | ✓ | — |
| Schema markup | ✓ | — |
| Page still excluded from search | — | ✓ |
| Password protection left on | — | ✓ |
| Links that go nowhere | — | ✓ |
| Placeholder text | — | ✓ |
| Staging addresses in links | — | ✓ |
| Inside components | — | ✓ |
The last row is why this extension exists. Putting your header and footer in a component and reusing them across a site is normal practice, and one dead link in there is a dead link on every page. Even so, the inside of a component is documented as out of scope for those built-in checks.
How it behaves
Click the row and the component’s canvas opens with the element selected. It also tells you in how many places that component is used, so you can see that fixing it once fixes all of them.
Hide them from later checks — one finding, one page, one component, or a whole kind at a time. Results always show how much was looked at separately from how much was found.
It does not promise to find everything, so every result lists what was left out: forms are skipped whole (apps must not read login or password fields); placeholder text is matched against five English phrases only; values inside a component that are set where the component is placed are not read; CMS collection content is not checked; page bodies are only checked when you run that check.
It reads, and it moves you around in the Designer. Findings are not stored anywhere and disappear when you close the panel — only your ignore list stays, in your own browser.
Pricing
| Free | $9 / month | |
|---|---|---|
| Check the page settings on every page | ✓ | ✓ |
| Jump to what it found | ✓ | ✓ |
| Ignore list | ✓ | ✓ |
| Check inside components | — | ✓ |
| Check page bodies | — | ✓ |
The paid plan is bought from this app’s page in the Webflow App Marketplace — the same page you installed GoLive Check from. The extension points you there whenever it holds a feature back, so you never have to go looking for it.
A subscription covers one Webflow site. Billing is handled by Webflow through the App Marketplace — GoLive Check never sees your payment details. Cancel from Webflow at any time; the free checks keep working.
Install GoLive Check from the Webflow App Marketplace and authorize it for the site you want to check. Then open that site in the Webflow Designer, open the Apps panel, and launch GoLive Check. It appears as a panel next to your canvas. The − and + buttons in its top-right corner make it a step smaller or a step wider each time you press them. It opens at the standard size each time.
Nothing runs until you press a button. GoLive Check never starts a check on its own.
| Button | What it looks at | How long |
|---|---|---|
| Quick check | Page settings for every page — excluded from site search, password protection — plus site-wide password protection, plus everything inside your components on the paid plan. Utility pages (404, password), CMS template pages and template style-guide pages are left out on purpose, and the panel names them and says why. | A second or two. |
| Full check | Everything above, and the elements sitting on the pages themselves — links that go nowhere, placeholder text, staging URLs. Part of the paid plan. | It depends on how much is on your pages, not just how many of them there are. Two measured runs, both four pages: one with 31 elements finished in under four seconds, one with 1,851 elements took twenty-five. A large site can take several minutes. It shows you which page it is on while it runs. |
Both buttons are there from the moment the panel opens, so you can see what each one covers before you press anything. On the paid plan you can press either one first: Full check runs the quick pass itself and then goes on to the page bodies, so you get one combined result.
Close any component you have open first. While you are editing a component, the Designer reports the component’s contents instead of the page’s, which would produce a quietly different answer. If GoLive Check cannot get out of the component on its own, it stops and says so rather than showing you numbers it does not trust. When it does move around your site to read the pages, it puts you back on the page you started from — including when the check fails part-way.
The panel answers in four parts, top to bottom:
| Headline | “Found 4 issues in 6 pages and 3 components”, or “Nothing to fix in what was checked”. It always names the scope, because “nothing found” means nothing without it. |
|---|---|
| Looked at… | How much was actually read: page settings, pages in full, components, elements. This is the count of what was examined, not what was wrong. |
| What to fix | Grouped by kind — Excluded from search, Password protected, Link goes nowhere, Placeholder text, Staging URL — with a count on each group, and a line under each group saying what that kind means. Each row names the page or the component it is in; for a component it also says in how many places that component is used, because fixing it once fixes all of them. |
| What this check did not look at | The edges of the answer: pages that were skipped and why, components that could not be opened, forms that were skipped, anything behind the paid plan, and the known limits. Read this before you treat a clean result as a clean site. |
A count of results hidden by your ignore list is shown too, so the numbers never shrink silently.
Every finding has a button that takes you to it in the Designer. It only navigates and selects; it never edits anything.
If the element has been deleted since the check ran, the panel says so and asks you to run the check again. It always answers — a button that appears to do nothing is a bug, not a result.
Some findings are intentional: a page you are deliberately keeping out of search, a placeholder you have not written yet. Press Ignore… on a finding and choose how far the decision should reach:
| just this one | This single finding, and nothing else. Start here. |
|---|---|
| on this page | This kind of problem, anywhere on this page. |
| in this component | This kind of problem, anywhere inside this component. |
| everywhere | This kind of problem across the whole site. The widest option — it will also hide problems you have not seen yet. |
Ignored items are listed at the bottom of the panel with a Show again button next to each, and the count of what is hidden stays on screen. Renaming a page or a component does not break an ignore rule.
The list is kept in this browser, for this site. It does not follow you to another computer, another browser or another profile, and it survives app updates. If a saved rule is ever found damaged, GoLive Check removes it, shows the findings it was hiding again, and tells you it did so.
GoLive Check never changes your site, so nothing it does needs undoing. If a check stops, the panel says why rather than going quiet. When the cause is something you can fix — a component left open, for instance — the result you already had stays on screen, so fixing it and pressing the button again is all that is needed. See Support below.
Email firstpenguinapps38@gmail.com. The extension shows a Site ID at the bottom of its panel — including it helps us answer faster.