Technical SEO audit and implementation for a live website or online store
We audit the technical side of a live website or online store and confirm what stops search engines from crawling, rendering or indexing the pages that matter. The issues you approve are then fixed in the template, setting, redirect or code that causes them, and the same checks run on the live site after release.
Norml finds the technical reasons search engines miss or misread a site's important pages, and fixes them. The work can be an audit on its own, an audit followed by the fixes, or the implementation of an audit you already have, on WordPress, WooCommerce, Shopify or a site built with a JavaScript framework.
What the audit and the fixes cover
Every finding names the URLs it affects, the template or setting behind it and the check that will show it is fixed. Each part below applies only where the findings call for it.
Crawling and indexingWe crawl the site with a smartphone user agent, as Google does, and compare the results with the XML sitemap and the Search Console page indexing report. The findings list important pages that robots rules or noindex tags block, pages that return errors or sit behind redirect chains, and pages Google has not indexed.
01
Duplicate URLs and page signalsWhere one page can be reached at several addresses, we compare the canonical Google chose with the one the page declares, then point canonical tags, redirects and internal links at a single version. Missing or duplicated titles, meta descriptions and H1s are grouped by template, so one template fix can correct many pages.
02
Site structure and internal linksThe crawl, set against the sitemap and Search Console, shows pages that no internal link reaches, important pages several clicks away from the homepage, and links that still point at redirected or non-canonical URLs. Fixes go into the menus, footers, templates and category pages that hold those links. When the findings call for new or merged pages, we agree the page plan with you before anything moves.
03
Structured data for what the page showsMarkup for the organization, breadcrumbs, articles, products or services is added only where it describes what the page visibly shows. Each type is checked on the live page with a markup validator, and whether rich results appear stays Google's decision.
04
Pages rendered with JavaScriptOn sites built with React or another JavaScript framework, we check the HTML the server returns against the page after its scripts run. Content, titles, canonical tags and structured data should be there without a click, links need real URLs, and each route should return the right status code when opened directly. The fix is made in the shared component or the rendering setup responsible.
05
Catalog and filter pagesOn an online store, filters and sort orders can turn one category into many URLs that list the same products. We agree with you which category and filter combinations deserve their own indexable pages, and only those go in the sitemap. Robots rules, canonical tags and internal links then point search engines away from the other combinations, while paginated category pages keep their own URLs so every product stays reachable.
06
Search Console and sitemapsWith access to Search Console, we confirm that the property covers the site's canonical address and its ownership is verified, that the submitted sitemap lists only canonical, indexable pages, and that robots rules do not block the files pages need to render.
07
Related work on technical SEO, site structure and staged releases
Shows our technical SEO on a live WordPress site. For a Manhattan co-working company, we fixed long-standing technical issues, optimized every product page and built the Airtable system its editor uses to manage location pages.
Shows technical SEO on an online store: for a retailer of instant cameras and film, we fixed technical issues and built content while the site was rebuilt piece by piece.
Shows how we plan site structure for search: a personal injury firm's website was planned as one hierarchy, with its own page and URL for each practice area and sub-practice, and pages for its Southwest Florida locations.
Shows how we release changes on a site whose lead generation runs mostly through search and paid traffic: a dietitian platform's new custom WordPress theme went live in slices, header first, with traffic and tracking checked before each next slice.
Search data from Google and your analyticsUser access to your Search Console property and analytics account, so the findings rest on Google's own indexing data and real visits as well as our crawl.
01
Access to the site and its codeAn admin account for the CMS or store, the theme files or code repository, and a staging copy where one exists, with each account in the name of the person using it.
02
The pages that matterThe templates, categories and pages that bring in business, any URLs that are not indexed or do not appear for the searches they target, and site changes you already have planned.
03
Earlier audits and reportsAny audit, crawl export or developer notes you already have, including an audit from another provider and the tool it was run with.
04
A decision-maker for changesOne person on your side who chooses which fixes go ahead and when they are released.
05
How an audit and its fixes run
[Agree the coverage]
We agree which sections, templates and URLs the audit covers, then connect to Search Console and analytics before the first crawl.
Step 01
[Crawl and inspect]
A full crawl, Search Console's indexing and canonical data, and the returned and rendered HTML of representative page types are recorded as the baseline.
Step 02
[Confirm each cause]
Each issue is reproduced on the live site and traced to the template, setting, plugin or component behind it. Anything that cannot be confirmed is marked as a hypothesis.
Step 03
[Choose the fixes]
You get the findings in order of priority, with the pages each one affects and the change it needs. You decide what goes ahead; an audit ordered on its own ends here, with the report.
Step 04
[Fix on staging]
Approved fixes go to a staging copy first where the platform has one, and the affected page types are tested there before release.
Step 05
[Release and check again]
After release, the same crawl and page checks run on the live URLs. Changes that need Google to recrawl the pages are listed separately, with the Search Console report that will show them.
No account layer between you and them. These are the Norml specialists this work runs through.
Let's chat
“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”
We already have an audit from another provider. Can you implement it?
Yes. Before any change, each item is checked against the live site and Google's current documentation. Items that are already fixed, out of date or not supported by that documentation are listed with the reason, and the rest become the agreed fixes. Once the fixes are live, the audit's checks run again with the same tool and settings where possible, so each item can be compared with its original finding.
Can we order the audit without the implementation?
Yes. The report then gives each finding with the affected URLs, its cause and the change it needs, so your developers can make the fix. Implementation can be added later, after a check that each finding still applies to the live site.
Can you find out why specific pages are not ranking?
We can check the technical reasons for the URLs you name: whether Google indexed each one, which canonical it chose, whether another URL such as a filter or variant page appears for the search instead, and which internal links reach it. Ranking also depends on content, competing pages and links, so the report separates confirmed technical causes from questions a technical audit cannot settle.
Will the fixes change how our site looks?
No, unless you choose a change that does. Representative pages are compared at phone and desktop sizes before each release, and a fix that would alter the design, such as moving a menu or adding text to a category page, comes to you as a decision first.
How does the work differ by platform?
On WordPress and WooCommerce, changes are made in the theme, plugin settings or redirect rules; on Shopify, in theme templates and store settings; on a site built with React or another JavaScript framework, in its components and rendering setup. Where a platform sets part of the URL structure itself, the report says what can and cannot change.
Do we need to rebuild a JavaScript site to fix its SEO?
Not necessarily. The audit shows which routes lose content, links or metadata when crawled, and each is fixed in the component responsible where that is possible. Rendering some routes on the server is recommended only for routes that cannot be fixed that way, and it is planned with your developers.
Does the audit include Core Web Vitals?
It records them. Where Google has enough real-visit data, the report shows which page groups fail and the templates they share. Fixing the causes, such as heavy images, blocking scripts or cache settings, is scoped as separate performance work with its own before-and-after tests.
Do these fixes matter for Google's AI Overviews?
They are a precondition. Google can show a page as a supporting link in AI Overviews or AI Mode only if the page is indexed and eligible to appear in Search with a snippet, so the same crawling and indexing fixes apply. Tracking whether AI tools cite your pages, and writing content for those answers, is separate work.
Can you work with our developers or agency?
Yes. Fixes can go to your developers as written specifications, or we make them ourselves through your usual review and release process. Either way, each fix is checked on the live site once it is out.
Will this get our pages indexed and ranking?
We can't promise that. Google decides what it indexes and how pages rank. The work removes technical reasons a page cannot be crawled, rendered or understood, and the report shows which of those reasons are gone.
What happens when a fix needs content, links or a rebuild?
The report names that finding and the work it needs, and that work is scoped on its own. This applies to content writing, keyword research, link building, redesigns and theme rebuilds, platform moves, and setting up analytics or conversion tracking.
See more of our website and SEO work
The case studies describe each site before the work and the changes we made to its pages, templates and structure.