Search Atlas Help Center

🔧 Fix Specific Site Audit SEO Issues by Page

Open in
View as Markdown Open in ChatGPT Open in Claude
Camilo Aponte

Camilo Aponte

Last updated on Sep 30, 2026

🗺️ How to Navigate to a Specific Issue

Every flagged item in the Site Audit links directly to the affected page and issue type. To reach the fix view, open the Site Audit report, click the issue count next to any category, then click an individual URL to see all issues flagged for that page. Use the sections below to act on each issue type once you land there.

🧩 Schema Markup Issues

Schema errors tell search engines your structured data is incomplete or invalid, which can prevent rich results from appearing.

  1. Missing schema: Identify the page type (article, product, FAQ, local business). Add the matching JSON-LD block inside a <script type="application/ld+json"> tag in the <head>. Use schema.org for the required properties for each type.
  2. Invalid or incomplete schema: Copy your existing JSON-LD into Google's Rich Results Test. Fix every property marked as missing or incorrect, then re-validate before republishing.
  3. Duplicate schema blocks: Remove all but one JSON-LD block of the same type per page. Duplicates cause parsing conflicts and can suppress rich results.

🖼️ Image Optimization Issues

Unoptimized images slow page load and miss accessibility signals that search engines use for ranking.

  1. Missing alt text: Add a descriptive alt attribute to every <img> tag. Example — Before:<img src="shoe.jpg"> | After:<img src="shoe.jpg" alt="Red running shoe with white sole">. Keep alt text under 125 characters and avoid keyword stuffing.
  2. Oversized file size: Compress images to under 150 KB where possible. Use WebP format instead of PNG or JPEG. Tools like Squoosh or ShortPixel can batch-compress your library without visible quality loss.
  3. Missing width and height attributes: Add explicit width and height values to every <img> tag to prevent Cumulative Layout Shift (CLS), which directly impacts Core Web Vitals scores.

📝 Page Title Issues

Page titles are one of the highest-impact on-page SEO elements. Search Atlas flags titles that are too short, too long, missing, or duplicated.

  1. Title too long (over 60 characters): Trim the title so the primary keyword appears within the first 60 characters. Everything beyond roughly 580 px of rendered width is truncated in search results.
  2. Title too short (under 30 characters): Expand the title to include your primary keyword and a secondary modifier or brand name. A strong structure is: Primary Keyword – Secondary Modifier | Brand.
  3. Missing title tag: Add a <title> tag inside the <head> of the page. Every page must have exactly one unique title tag.
  4. Duplicate titles: Open Content → Meta Generator in the left sidebar to generate unique, keyword-targeted titles for each affected URL at scale.

🔗 Link Issues

Link issues split into two categories: broken links that return errors and internal linking gaps that limit crawl depth and authority flow.

  1. Broken internal or external links (4xx/5xx): Click the flagged URL in the Site Audit to see the exact broken link and the page it lives on. Fix internal broken links by updating the href to the correct destination URL, or redirect the broken target with a 301. For broken external links, replace them with a working equivalent or remove them entirely.
  2. Orphaned pages (no internal links pointing to them): Navigate to Content → On-Page Audit in the left sidebar, enter the orphaned page's URL, and use the internal linking suggestions to find contextually relevant pages on your site that should link to it. Add those links in your CMS.
  3. Low internal link count: Use the Page Explorer integration inside the Site Audit to identify high-authority pages on your domain. Add contextual anchor-text links from those pages to the under-linked URL, prioritising anchors that include the target page's primary keyword.

⚡ Technical Performance Issues

Technical issues affect page speed and crawlability. The two most common flags are render-blocking resources and uncompressed assets.

  1. CSS and JavaScript not minified: Enable minification in your CMS or build tool. In WordPress, plugins such as WP Rocket or NitroPack handle this automatically. In custom builds, add a minification step to your deployment pipeline (e.g., using Terser for JS and CSSNano for CSS). After enabling, re-run the Site Audit to confirm the flag clears.
  2. Compression not enabled (Gzip/Brotli): Enable Gzip or Brotli compression at the server or CDN level. For Apache, add mod_deflate rules to your .htaccess. For Nginx, set gzip on; in your config. Most CDNs (Cloudflare, Fastly) offer a one-click compression toggle in their dashboard.
  3. Render-blocking resources: Move non-critical CSS to load asynchronously and add defer or async attributes to non-essential JavaScript tags so they do not block the initial page render.

🎨 Inline Style Issues

Inline styles (style attributes written directly on HTML elements) bloat page HTML, make maintenance harder, and can conflict with your site's CSS cascade.

  1. Search your page's source for style=" to locate all inline declarations.
  2. Move each style rule into your external stylesheet, assigning a class or ID to the element instead.
  3. Before:<p style="color: red; font-size: 14px;"> | After:<p class="note-text"> with .note-text { color: red; font-size: 14px; } in your CSS file.
  4. If your CMS page builder injects inline styles automatically, switch to a CSS custom properties or theme settings approach within the builder to keep styling out of the HTML markup.

✅ Verifying Your Fixes

After making changes, return to the Site Audit and click Recrawl on the affected project. Once the crawl completes, open the same issue category and confirm the flagged URLs no longer appear. For titles and meta descriptions, you can also use Content → Meta Generator to audit and update metadata in bulk before re-crawling.

💬 Need More Help?

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.