Optimization of website pages
FIXES FOR GOOGLE

Fixes for Google: Correcting Technical and On-Page Errors in Your Package

Fixes are the fourth stage of the SEO Optimization package. By this point, the site audit has identified the errors, keywords have been assigned, and content has been optimized. Now we implement the technical corrections flagged during the audit - the changes that directly affect how Google crawls, interprets, and ranks your pages.

Not every error found in the audit is fixed in this stage. We work through a priority list: errors with direct ranking impact first, then usability issues, then lower-priority refinements. What gets fixed depends on what was found on your site.

Categories of Errors We Fix

Indexation errors

Pages that should be indexed but are not. Common causes:

• `noindex` directive left in the page source from a development or staging phase
• Pages blocked in `robots.txt` unintentionally
• Pages returning incorrect HTTP status codes (soft 404 - a page returns 200 but shows "not found" content)
• Canonical tags pointing to the wrong URL, causing Google to skip the actual page

We identify which pages are failing to appear in the Google index and trace the cause to the specific directive or configuration error.

Redirect issues

Redirect chains - where URL A redirects to URL B which redirects to URL C - dilute link equity and slow down crawling. We consolidate redirect chains to single-hop 301 redirects wherever possible.

We also fix redirect loops (A → B → A), which cause crawler errors and prevent the pages involved from being indexed at all.

Duplicate content

Duplicate content occurs when the same or near-identical content appears at multiple URLs. Google selects one version to rank and may ignore the others. Common sources:

• HTTP and HTTPS versions of the same page both accessible without a redirect
• www and non-www versions both accessible
• URL parameters creating duplicate pages (`/page?sort=asc` and `/page?sort=desc` showing identical content)
• Category pages and filtered views with the same products in different order

We fix duplicate content through canonical tags, 301 redirects, or parameter handling - depending on which solution fits the specific case.

Page speed issues flagged in the audit

If the site audit identified specific, fixable speed issues, we address them in this stage:

• Image files that are oversized for their display dimensions (a 2MB image displayed at 400px width)
• Missing image compression (WebP conversion for JPEG/PNG assets)
• Render-blocking CSS or JavaScript in the page head that delays first content paint
• Missing browser cache headers on static assets

We do not redesign the site's architecture or replace its hosting infrastructure. Speed improvements in this stage address the specific issues identified in the audit.

Broken links

Internal links pointing to pages that return 404 errors waste crawl budget and create a poor user experience. We locate internal broken links across your site and update them to the correct current URLs.

For external broken links on high-value pages, we flag them in the work report - fixing external links requires either removing them or replacing them, which depends on the context of each link.

Structured data errors

If your site has existing schema markup (JSON-LD or microdata), we check it against Google's current requirements using the Rich Results Test. Common errors:

• Required fields missing (a Product schema without a `name` or `offers` field)
• Incorrect data types (passing a string where a URL is required)
• Schema present in the HTML but not rendering because it is injected by JavaScript without server-side fallback

We correct existing schema errors. Adding new schema types to pages that have none is a separate scope item - noted in the work report.

Mobile usability issues

Flagged items from Google Search Console's Mobile Usability report:

• Text too small to read without zooming (font size below 12px on mobile)
• Clickable elements too close together (buttons or links with less than 8px spacing)
• Content wider than the screen (horizontal scroll on mobile)
• Viewport meta tag missing or misconfigured

What We Do Not Fix in This Stage

The fixes stage addresses errors with direct search impact. It does not include:

• Complete site redesign or template changes
• Writing new content for pages identified as thin
• Building backlinks or addressing off-page ranking signals
• Fixing errors on pages outside your package page count

Items outside scope are documented in the work report so you have a complete picture of remaining issues.

How Package Size Affects the Fixes Stage

Package 20 ($199): All critical errors across up to 20 pages. Priority: indexation issues, redirects, duplicate content, mobile usability.

Package 50 ($349): All critical errors across up to 50 pages. Additional scope: speed improvements where individual assets can be addressed without infrastructure changes.

Package 100 ($599): All critical and moderate-priority errors across up to 100 pages. Includes structured data error correction on pages with existing schema.

Package BIG ($1,199): Full error remediation across all pages. Includes systematic redirect chain consolidation, duplicate URL resolution via parameter handling, and schema validation across all template types.

The Sequence: Fixes After Optimization, Not Before

Fixes are performed after content optimization - not before. The reason: content optimization may change page titles, meta descriptions, and heading structure. Some errors identified in the audit (missing H1, duplicate meta descriptions) are resolved during content optimization, not in the fixes stage. Performing fixes before optimization would mean correcting errors that are about to be edited anyway.

The exception is indexation errors: if pages are not indexable, content optimization on those pages has no visible effect. When the audit identifies pages blocked from indexing, we resolve those blocks first, before starting content work.

What You Receive After This Stage

• Complete list of all corrections made, with before/after documentation for each
• List of errors that were identified but fall outside the package scope, with recommendations
• Updated crawl error status - confirmation that previously flagged pages are now accessible
• Notes on any errors that require your access or decision to resolve (for example: a plugin causing redirect loops that requires a configuration change in your CMS)

This list becomes part of the final work report.

Frequently Asked Questions

How do you know which pages have errors? The SEO site audit (stage 1 of the package) produces a full list of errors across your site. We use Google Search Console data, Screaming Frog or Sitebulb crawls, and PageSpeed Insights to identify issues. The fixes stage works directly from this audit output.

Can you fix errors on pages outside my package count? We document all errors found across the full site in the work report, regardless of package size. Corrections are applied only to pages within the package scope. For errors on other pages, the documentation gives you or another specialist what is needed to address them.

What if an error requires access to the server or hosting panel? Some fixes - particularly hosting-level cache configuration and server redirect rules - require access beyond the CMS. In these cases, we provide exact specifications and, where possible, the configuration code or settings to implement. We do not require server access by default but can work with it if you choose to provide it.

Will fixing errors cause any downtime? No. Most corrections - canonical tags, meta tags, robots.txt adjustments - involve file or database edits with no service interruption. Redirect changes take effect immediately without downtime. Speed-related changes to assets are also non-disruptive.

How quickly do fixes affect Google rankings? Google needs to recrawl the corrected pages before ranking changes reflect. For a regularly crawled site, expect 2-4 weeks for most fixes to be processed by Google. Indexation errors that have kept pages out of the index entirely may take 4-8 weeks to fully resolve as Google recrawls and reindexes the affected pages.

What if the same errors appear again after the package is complete? Some errors recur if the underlying process is not changed - for example, if a CMS plugin generates duplicate URLs automatically, fixing the existing duplicates does not prevent new ones. We document these systemic causes in the work report so they can be addressed at the source.