Fix common issues

Step by step fixes, with copy-ready code, for the problems the audit finds most often.

How to use this page

Find the issue from your audit report below. Each fix explains what the problem is in plain words, then how to fix it. If you use a website builder such as WordPress, Shopify, Wix, Squarespace or Webflow, most fixes live in the page or SEO settings rather than in code.

Not sure which issues affect your page? Run the free SEO audit tool to check titles, indexability, links, schema and AI search readiness without an account. Use the report's evidence to choose the relevant fixes below, then re-run the audit after making changes.

Tip: The report's AI fix prompt lists all your issues with evidence. Paste it into ChatGPT or Claude together with your page's code and ask for the exact changes.

Title tag missing, too long or duplicated

The title tag is the headline Google shows in results. Every page needs its own. Aim for 50 to 60 characters, put the main topic first and your brand last.

html
<title>Cold Brew Coffee: A Simple 12-Hour Recipe | Brewlab</title>

Preview it in the SERP simulator, which measures the title in pixels the way Google does, and use the meta tag checker to find missing or duplicate tags.

Meta description missing

The meta description is the short summary under your title in the results. It does not change rankings directly, but a clear one earns more clicks. Aim for 140 to 160 characters that say what the reader gets.

html
<meta name="description" content="Make smooth cold brew at home with just coffee, water and 12 hours. Ratios, grind size and how to store it." />

The SERP simulator shows where your description gets cut off on desktop and mobile.

Missing or multiple H1 headings

The H1 is the main title on the page itself. Use exactly one, make it describe the page, and use H2 and H3 headings for the sections below it. Many themes turn the logo into an H1 by mistake: the H1 and heading checker shows the page's whole heading outline, so a stray H1 or a skipped level stands out.

Page cannot be indexed

If the audit says a page is set to noindex, Google will not show it. Search the HTML for this line and remove it from pages you want in search:

html
<meta name="robots" content="noindex" />

The same instruction can also come from an HTTP header called X-Robots-Tag, which your hosting or a plugin sets. On WordPress, check Settings, Reading for "Discourage search engines" and your SEO plugin's per-page setting.

The indexability checker tests the status code, robots.txt, the meta tag, the header and the canonical in one go. The HTTP header checker shows an X-Robots-Tag that the page source hides.

Blocked by robots.txt

A Disallow rule in robots.txt stops crawlers from reading matching pages. A common accident is a staging rule that blocks everything:

text
User-agent: *
Disallow: /

Allow the whole site and point crawlers to your sitemap instead:

text
User-agent: *
Allow: /

Sitemap: https://brewlab.coffee/sitemap.xml

The free robots.txt generator builds a correct file for you, and the robots.txt tester checks any page against your live file.

Canonical missing or pointing elsewhere

A canonical tag names the main address of a page. Add a self-referencing canonical to every page you want indexed, using the full address:

html
<link rel="canonical" href="https://brewlab.coffee/guides/cold-brew" />

If the audit says the canonical points to a different page, Google will likely index that page instead. Fix the tag unless the duplicate is intentional. The canonical URL checker confirms the canonical address loads, can be indexed and does not conflict with other signals.

No sitemap, or not listed in robots.txt

Create a sitemap at /sitemap.xml listing your important pages, add a Sitemap: line to robots.txt, and submit it in Google Search Console. Most platforms generate one automatically. Otherwise use the free sitemap.xml generator. Either way, the sitemap checker confirms the file is valid and that the pages it lists load.

Images without alt text, too large, or without dimensions

  • Alt text: describe what the image shows in a few words. Decorative images can use an empty alt="".
  • Size: export photos at the size they are shown, and use WebP or AVIF. A 4 MB photo can slow a page by seconds.
  • Dimensions: set width and height so the browser reserves space and the layout does not jump.
  • Lazy loading: add loading="lazy" to images below the fold, but never to the main image at the top.
html
<img src="/img/cold-brew-jar.webp" alt="Cold brew coffee steeping in a glass jar" width="1200" height="800" loading="lazy" />

The image SEO checker lists every image on a page with its alt text, dimensions, file size and format.

Slow page or poor Core Web Vitals

Run Lighthouse to see what is slow, or the free page speed checker without an account, then work through the usual causes: oversized images, too much JavaScript, slow web fonts, and a slow server. The Lighthouse page explains each metric and its fixes.

Links to pages that return an error waste crawl time and frustrate visitors. Update each broken link to a working page or remove it. When a page moves, add a single permanent (301) redirect from the old address to the new one, and update internal links to point straight to the new address instead of through the redirect.

The broken link checker tests every link on a page, and the redirect checker shows each hop of a redirect with its status code.

Not using HTTPS, or mixed content

Every page should load over HTTPS, and every image, script and stylesheet on it should too. Most hosts offer free certificates. Redirect all http:// addresses to https:// with a 301. The SSL certificate checker tests the certificate and its expiry date, the redirect from HTTP, HSTS and mixed content.

Structured data missing or invalid

Structured data describes your page to machines. Pick the type that matches the page: Organization for your homepage, Article for posts, Product for products, LocalBusiness for a local shop, FAQPage for a genuine FAQ. The free schema generator writes valid JSON-LD for you.

html
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Brewlab",
  "url": "https://brewlab.coffee",
  "logo": "https://brewlab.coffee/logo.png"
}
</script>

If the audit reports invalid markup, the evidence names the field. The most common mistakes are missing required fields and prices or dates in the wrong format. Paste the corrected code into the schema validator to check it before you publish.

No llms.txt

An llms.txt file at /llms.txt gives AI tools a short, readable summary of your site and links to your key pages. Use the free llms.txt generator, upload the file to the root of your site, then check it with the llms.txt checker.

AI crawlers blocked

If your robots.txt blocks OAI-SearchBot, PerplexityBot, ClaudeBot or similar crawlers, those engines cannot read or cite you. Remove the rules for the crawlers you want in answers. You can still block training-only crawlers such as GPTBot if you prefer. See AI visibility.

If robots.txt allows them and the audit still reports them blocked, your CDN or firewall is turning them away. The AI crawler checker tests both, and shows the page as those crawlers see it without JavaScript.

Missing social tags

Open Graph tags control the title, description and image shown when your page is shared on LinkedIn, Slack, WhatsApp and elsewhere:

html
<meta property="og:title" content="Cold Brew Coffee: A Simple 12-Hour Recipe" />
<meta property="og:description" content="Smooth cold brew with just coffee, water and time." />
<meta property="og:image" content="https://brewlab.coffee/img/cold-brew-share.jpg" />

Preview the result with the Open Graph checker. If you have no share image, make one at 1200 by 630 pixels with the OG image generator.

Hreflang errors

If your site has versions for different languages or countries, each version should list every version, itself included, with valid codes such as en-gb or fr. Every version must link back to the others, or search engines ignore the tags.

html
<link rel="alternate" hreflang="en-gb" href="https://brewlab.coffee/uk/" />
<link rel="alternate" hreflang="en-us" href="https://brewlab.coffee/us/" />
<link rel="alternate" hreflang="x-default" href="https://brewlab.coffee/" />

The hreflang checker validates every code and tests that each alternate loads, can be indexed and links back.

Thin content or no clear answer

If a page is short, vague or never answers the question its title promises, both Google and AI engines will prefer another page. Open with a direct answer in the first two sentences, then add the details, steps, examples and evidence a reader needs. Length is not the goal: completeness is.

Missing trust signals (E-E-A-T)

Show who is behind the content. Add an author name with a short bio on articles, an About page, a way to contact you, and sources for the claims you make. For products and services, show real reviews and clear policies.

Mobile problems

Every page needs a viewport tag, readable text without zooming, and buttons large enough to tap:

html
<meta name="viewport" content="width=device-width, initial-scale=1" />

If the audit reports horizontal scrolling, something on the page is wider than the screen, often a table, a wide image or an embedded video without a maximum width. The mobile-friendly test shows the page as Google renders it on a phone.