Technical SEO Fixes
How Technical SEO Fixes works, how to set up the script, what each fix does, and what to do when something goes wrong.
Technical SEO Fixes finds problems on your site that search engines and AI assistants care about, writes a fix for each one, and applies the fixes you approve. You don't edit your site's code or templates. One small script on your site applies the fixes.
This guide covers how it works, how to set it up, what each fix does, and what to do when something goes wrong.
How it works
- We scan your site. We read up to 60 of your most important pages and look for missing or weak page titles, descriptions, image text, structured data and more.
- We suggest fixes. Each problem gets a suggested fix that you can read before anything changes.
- You review and apply. You tick the fixes you want and click Apply. Nothing changes on your site until you do.
- The script applies them. A script on your site adds the approved fixes to each page as it loads. Your original content stays as it is in your CMS, so turning a fix off brings the page straight back.
- We keep checking. We check your site after every Apply and again every week, so we notice if the script is removed or a fix stops showing.
You find Technical SEO Fixes on the Site Audit page, in the banner above your scores.
Setting up the script
You add the script once. It works on every page from then on.
On WordPress with our plugin
If your site runs our WordPress plugin, you have nothing to paste. When you apply fixes for the first time, the app asks you to confirm, then the plugin adds the script for you.
- On a recent plugin version this takes about a minute.
- On an older version it happens on the plugin's next sync, within about 15 minutes.
If the script still can't be found a day after your first Apply, the app shows the manual steps instead.
On any other site
Copy the script from the Connect your site window and paste it into the <head> section that every page of your site uses. Then publish your site and click Check installation.
Where to paste it:
| Platform | Where the script goes |
|---|---|
| WordPress without our plugin | A header-scripts plugin, or Appearance, Theme File Editor, header.php, inside <head> |
| Webflow | Site Settings, Custom Code tab, Head Code. Then publish your site. |
| Shopify | Online Store, Themes, then Edit code on your live theme. Open Layout, theme.liquid, and paste inside <head>, before {{ content_for_header }}. |
| Squarespace | Settings, Advanced, Code Injection, Header. Code Injection needs a Core, Plus or Advanced plan, or an older Business or Commerce plan. The Personal plan doesn't allow it. |
| Wix | Settings, Custom Code, Add Custom Code. Choose All pages and Head. Your site must be published on a connected domain. |
| Duda | Settings, Head HTML. Then republish your site. |
| Ghost | Settings, Code injection, Site Header |
| HubSpot | Settings, Content, Pages, choose your domain, then Site header HTML. This covers pages hosted on HubSpot only. If your homepage runs on another platform, add the script there. |
| Anything else | The shared header template that every page loads |
Paste the script into the shared header, not the homepage alone. A script on the homepage only can't apply fixes to your other pages.
After you click Check installation, you see "detected ✓" when we find the script. If you just published, wait a minute and click Check again.
Reviewing and applying fixes
Click Review fixes in the banner to open your fixes. They sit in three lists.
| List | What it holds |
|---|---|
| Ready to apply | Fixes from your scans that aren't on your site yet. "New in latest scan" fixes are listed apart from fixes found earlier. |
| Live on your site | Fixes that are running now. Untick one to turn it off. |
| Turned off | Fixes you turned off. Tick one to put it back. |
Each fix shows the current value from your page next to our suggestion. To change a suggestion, click it and edit the text, then save. Some fixes, such as image size attributes and the published date, come straight from your page and can't be edited.
When your choices are ready, click Apply. We update your site, which usually takes under a minute. Visitors see the change within about a minute after that.
Turning a fix off works the same way. Untick it, click Apply, and the page goes back to its original content.
Refreshing the scan
Click Refresh audit to scan your site again. You can refresh once a day. After a refresh finishes, the button shows when the next one is available. A scan that fails or is blocked never uses up your refresh, so you can fix the cause and try again straight away.
When you open Site Audit and your last scan is more than a month old, a new scan starts on its own.
What each fix does
Fixes for search engines and AI assistants
Visitors don't see these. They change the information search engines and AI assistants read from your page.
| Fix | What it changes |
|---|---|
| Page titles | The title shown in search results and browser tabs |
| Meta descriptions | The short summary shown under your link in search results |
| Brand name consistency | Tells search engines your business name, so it shows the same way everywhere |
| Image alt text | Describes each image for search engines and screen readers |
| Image size attributes | Gives each image its width and height, so the page doesn't jump while it loads |
| Organization schema | Structured data about your business: name, logo and social profiles |
| LocalBusiness schema | Your address, phone and opening hours as structured data, taken from your own pages |
| Article schema | Marks your blog posts as articles, with their headline |
| Breadcrumb schema | Shows where a page sits in your site, for example Home, then Services, then Roof repair |
| FAQ schema | Marks up a FAQ section that's already on your page, so search engines can read the questions and answers |
Fixes visitors can see
These add a block to your blog posts. We add them to articles only, never to your homepage, service pages or contact page. We add at most two blocks per article, and we place each block in your page's own layout and style.
| Fix | What visitors see |
|---|---|
| Key takeaways | A short list of 3 to 5 main points at the top of the article |
| FAQ content | Up to 5 questions and answers at the end of the article, written from the article's own content |
| Published date | A "Published:" line with the date the article went live |
Read these before you apply them. We write them from your article, but you know your business best.
How many pages get fixes
- Each scan reads up to 60 pages.
- Visible blocks go on up to 10 articles, chosen by importance.
- Pages with very little text are skipped.
Statuses in the banner
| Status | What it means | What to do |
|---|---|---|
| Ready to review | The script is installed and new fixes are waiting | Click Review fixes |
| Active | The script is installed and your fixes are live | Nothing |
| Installing automatically | Our WordPress plugin is adding the script | Wait a few minutes |
| Setup required | We can't find a working script on your site | Open Set up now and follow the note it shows |
| Site blocked | Your site's security is blocking our scanner | See "Your site is blocking our scanner" below |
| Can't see site | Your site didn't let our scanner read its pages | See "We can't see your site" below |
| Fixes retired | We took some fixes off your site | Open the list to see why |
Retired fixes
A fix is retired when it's no longer right for your page. We take it off your site, and it shows greyed out under Retired with the reason and the date.
| Reason shown | What happened |
|---|---|
| Your page now has this itself, so our fix is no longer needed. | You added your own version, for example your own meta description, so ours is no longer needed. |
| Your page changed, so this fix no longer matches it. | You rewrote the page, for example its main heading, so a title, description or content block we wrote no longer fits it. |
| This image is no longer on your page. | The image the fix described was removed. |
| Our updated rules no longer make this fix for this page. | We changed our rules, and the page no longer needs this fix. |
| Our updated rules no longer add this to this type of page. | We stopped adding this kind of fix to pages like this one. |
Fixes that copy what your page already says, such as schema, the published date and your brand name, update on their own when your page changes. A fix you edited stays as you wrote it. Text we wrote, such as titles and content blocks, waits for you: when you rewrite the page, a new version waits under Ready to apply with an Updated label. A fix you turned off comes back as a new suggestion only when what it would add has changed.
You don't need to do anything for a retired fix.
Troubleshooting
When something stops the script or our scanner, the banner names the cause. Find it below.
A speed plugin is delaying the script
Speed plugins such as WP Rocket, LiteSpeed Cache, Perfmatters and Autoptimize can hold scripts back until a visitor clicks or scrolls. Search engines never click, so our fixes never run.
- Open your speed plugin's JavaScript settings.
- Find the list of scripts it shouldn't delay. In WP Rocket this is Delay JavaScript execution, Excluded JavaScript Files. In Perfmatters it's Delay JavaScript, Exclusions. In LiteSpeed Cache it's Page Optimization, JS Delayed Excludes.
- Add this line: site-fix-cdn/snippet.js
- Save, then clear the plugin's cache.
- Back in the app, click Check again.
If you also use Cloudflare Rocket Loader, the script you copied from the app already tells it to skip our script.
SiteGround is hiding the script
SiteGround Optimizer's Combine JavaScript Files setting merges our script into one of its own files, where it can't run.
- In WordPress, open SiteGround Optimizer, then Frontend, then JavaScript.
- Turn off Combine JavaScript Files.
- Clear the SiteGround cache.
- Click Check again.
Something on your site removes the script's address
The script tag is on your page, but its address is empty, so the browser loads nothing. An optimization or security plugin usually causes this.
- Find the plugin that rewrites or lazy-loads scripts.
- Exclude site-fix-cdn/snippet.js from it.
- Clear its cache, then click Check again.
The script is on your site twice
The script runs only once, so nothing breaks. Keep one copy to keep things tidy. If our WordPress plugin adds the script for you, remove the copy you pasted by hand.
The script belongs to another site
Each site has its own script. The one on this site was copied from another site in your account, so it applies that site's fixes, not this one's. Copy the script from this site's Connect your site window, replace the old one, publish, and click Check again.
The script is only on your homepage
You pasted the script into the homepage's own settings instead of the shared header. Move it to the header that every page uses (see "Where to paste it" above), then click Check again.
The script is missing
We found the script before, but it's gone now, so your fixes aren't live. This often happens after a theme change or a site rebuild. Paste the script into the shared header again and click Check again. Your fixes come back as soon as we find it.
We couldn't open your homepage to check
We tried to check your script, but your homepage didn't load for us.
- Open your homepage in a browser and make sure it loads.
- If it does, your host or security plugin is probably blocking us. Ask them to allow our crawler's IP address, which the app shows with a copy button.
- Click Check again.
Your site is blocking our scanner
Your site's security, such as Cloudflare, Wordfence, Sucuri or your host's firewall, is stopping our scanner, so we can't suggest fixes.
- Open your firewall or security plugin.
- Add our crawler's IP address to its allowlist. The app shows it in the How to fix window.
- Come back and click Refresh audit. A blocked scan doesn't use up your daily refresh.
We can't see your site
Our scanner reached your site but couldn't read its pages. The site might have been down, slow, or showing an error when we scanned.
- Check that your site loads in a browser.
- If it does, allow our crawler's IP address as described above.
- Click Refresh audit.
Fixes from earlier scans stay available while this is unresolved, but some may be out of date.
Still stuck?
Open Get help from the menu and choose Contact support. Tell us which message you see, and we'll take a look.
Good to know
- Your content isn't edited. Fixes are applied as each page loads. Your CMS keeps your original text, so turning a fix off undoes it at once.
- Your site needs HTTPS. Technical SEO Fixes works on sites served over https://.
- Search engines and the script. Google runs JavaScript when it indexes pages, so it sees these fixes. Some other crawlers, including several AI assistants, read only the raw page and may not see them.
- Language. We write suggestions in your page's own language. The block headings "Key takeaways", "Frequently asked questions" and "Published:" are in English for now.
- If your account or site is closed. When a site is removed or the account is cancelled, the fixes stop. We keep them, so they come back if the site returns.