Before adding more content to a Webflow site, check whether the pages you already have are accessible, useful, and measured correctly. An SEO audit should help you decide what to fix first and show whether the fix worked.
Begin with the pages that support the business: product and service pages, important use cases, comparison content, and articles that bring in relevant visitors. Then include a representative sample from each CMS template. A problem in a shared template can affect many pages at once.
Define the question the audit needs to answer
A site that lost traffic after a migration needs a different investigation from one that has never attracted qualified visitors. Record what changed, when it changed, and which pages are affected before running a long checklist.
Give the reviewer access to Search Console and your analytics, alongside the site and CMS. Add a list of recent releases and known tracking changes. A technical crawl can show broken links or missing fields, but it won’t explain which pages generate useful inquiries.
Keep the evidence in one working document. Each issue should have affected URLs, a description of the observed behavior, a proposed fix, an owner, and a way to verify the result.
Check access and indexability
For each priority page, verify that the live address responds as intended and that it is available to the search engine. Review noindex settings, robots rules, and any access restrictions. Use Search Console’s URL inspection to investigate the page’s reported indexing state.
Robots.txt and noindex do different jobs. A crawl block does not reliably remove a URL from Google, and it can prevent the crawler from seeing a noindex instruction on the page. Review the intended outcome before changing either setting.
Keep staging and production separate in the audit. A rule that makes sense on a test environment may be wrong for the public site. Record the domain used in each test so the team can reproduce it.
Inspect the CMS output
Check several live pages from each Collection, including an older item and one with missing optional fields. Look for repeated titles, empty descriptions, broken images, incorrect links, and sections that display awkwardly when content is short or unusually long.
Review titles and headings against the subject of the page. A product page should identify the product and its purpose clearly. Adding variations of the same keyword to every heading can make the page harder to read without helping the buyer.
Check that important information exists as readable text. If an integration list or product comparison is only an image, the page is less useful to someone who cannot read that image. Include text that explains the information, and use appropriate image descriptions.
For duplicate or near-duplicate versions, check the canonical setup. Google recommends consistent canonical signals, including internal links and sitemap entries. A template accidentally pointing every article to the same canonical is worth investigating quickly.
Follow the links a buyer would use
Open a relevant article and follow its path to a product, service, or inquiry page. Check that the next step is easy to find and that the destination still fits the context.
Review important pages with few or no useful internal links. Ask where a reader would naturally need that information and add a link there. Navigation, related resources, and relevant passages in other pages all deserve a review.
Check old campaign and migration links as well. A redirect may get a visitor to the correct page, but updating your own internal link removes an unnecessary hop and makes maintenance easier. Prioritize broken destinations and redirect loops before minor wording changes.
Review performance where visitors feel it
Test the templates and journeys used by real visitors, including mobile. Look at loading, responsiveness, and layout movement. Google’s Core Web Vitals cover those aspects of the experience through LCP, INP, and CLS.
Use field data where it is available and diagnostic tests to investigate the cause. A single test result is a starting point for inspection. Check large media, third-party scripts, embedded tools, and interactions that add work to the page.
Agree what to preserve before removing scripts. An unused script is an easy candidate for cleanup; a CRM or consent dependency needs more care. Test the affected workflow after the change.
Separate a content problem from a technical one
A page can be indexed and fast while failing to answer the buyer’s question. Read priority pages for substance. Is the offer clear? Are limitations explained? Is a claim backed by evidence? Does the page have a useful next step?
Compare pages that appear to serve the same purpose. You may need to clarify their distinct roles, combine overlapping material, or improve the stronger page. Publishing another article on the same subject may add maintenance work without resolving the gap.
Prioritize fixes by impact and reach
| Priority | Example | Verification |
|---|---|---|
| Resolve a blocker | A priority page is inaccessible, unintentionally excluded, or connected to a broken inquiry journey. | Repeat the failed check on the live page and confirm the expected outcome. |
| Fix a shared defect | A CMS template creates the wrong canonical or omits useful page information. | Check several affected items after the template change. |
| Improve a valuable page | A product page leaves an important buying question unanswered. | Review the content change and monitor relevant page and inquiry metrics. |
| Clean up lower-impact issues | An older, low-priority page needs an editorial improvement. | Include it in the maintenance backlog with a clear owner. |
Record completed changes separately from performance outcomes. You can verify that a broken canonical was fixed immediately. Search performance may take longer to assess and can change for other reasons.
A useful audit ends with a manageable plan. If your team has a long report and no clear first action, reduce it to the issues that affect important pages or repeat across the site. Beqi can help review that work and implement the fixes in Webflow.
Client context: Dexterity
Our published Dexterity project summary describes service-page development, CMS structuring for independent publishing, and a performance optimization pass. These are different workstreams: inspect the implementation and measure each outcome separately. A diagnostic score alone does not establish a traffic or revenue gain.
Related reading
Written by
