Every issue SEOFIX checks for

Why it matters: If search engines can't load your homepage, they can't crawl or index the rest of your site from it.

How to fix: Check that your server is online and responding, your DNS is correct and your SSL certificate is valid.

Why it matters: A `Disallow: /` rule for Googlebot or all crawlers tells search engines not to crawl any page. Pages can drop out of search results.

How to fix: Remove or narrow the `Disallow: /` rule in robots.txt so only private areas are blocked.

Why it matters: robots.txt isn't required, but it's where search engines look for your sitemap location and crawl rules.

How to fix: Add a robots.txt at the site root that allows crawling and lists your sitemap.

Why it matters: Listing your sitemap in robots.txt helps every search engine find all of your important URLs.

How to fix: Add a line like `Sitemap: https://yourdomain.com/sitemap.xml` to robots.txt.

Why it matters: A sitemap tells search engines which pages matter and when they change — especially helpful for new or deep pages.

How to fix: Generate an XML sitemap (most CMSs can do this automatically) and reference it in robots.txt and Search Console.

Why it matters: Search engines ignore sitemaps they can't fetch or parse, so the URLs in it lose that discovery signal.

How to fix: Fix the sitemap URL or XML so it returns HTTP 200 and follows the sitemaps.org format.

Why it matters: Sitemaps should only contain final, indexable URLs. Errors and redirects waste crawl effort and send mixed signals.

How to fix: Remove or replace these URLs in the sitemap with their final, indexable versions.

Why it matters: Search engines can't crawl blocked pages, so they can't see their content, links or noindex tags.

How to fix: If the page should appear in search, allow it in robots.txt. If it's private, stop linking to it or use noindex instead.

Why it matters: Server errors stop search engines from reading the page. Persistent 5xx errors can remove pages from the index.

How to fix: Check server logs for this URL and fix the underlying error.

Why it matters: The request timed out or the connection failed. Search engines may hit the same problem.

How to fix: Check server performance and availability for this URL.

Why it matters: Each extra hop slows users and crawlers and can dilute signals. Search engines may stop following long chains.

How to fix: Point the first URL (and links to it) straight at the final destination.

Why it matters: The URL never reaches a final page, so neither users nor search engines can load it.

How to fix: Fix the redirect rules so the URL resolves to a single final page.

Why it matters: Pages only found in the sitemap get little internal authority and are harder for users and crawlers to reach.

How to fix: Link to this page from relevant pages (navigation, related content, hub pages) — or remove it from the sitemap if it shouldn't exist.

Why it matters: Pages more than 3 clicks from the homepage tend to be crawled less often and receive less internal link value.

How to fix: Link to it from a higher-level page such as a category, hub or the navigation.

Why it matters: Links to missing pages waste crawl budget, leak link value and frustrate visitors.

How to fix: Update the links to point at a live page, or restore/redirect the missing URL to its best replacement.

Why it matters: Linking directly to the final URL saves a redirect hop for every visitor and crawler.

How to fix: Update these links to point at the final destination URL.

Why it matters: Links to dead external pages hurt user experience and can look like neglected content. (Sites that block automated checkers with 401/403/429 are not reported here.)

How to fix: Update or remove links to external pages that no longer exist.

Why it matters: A noindex directive on your homepage asks search engines to drop it from results — usually a leftover from a staging site.

How to fix: Remove `noindex` from the homepage's robots meta tag or X-Robots-Tag header.

Why it matters: A page you link to from many places is often important, yet noindex keeps it out of search results. This is fine for pages like account or thank-you pages, but worth confirming for anything you want found in search.

How to fix: Confirm whether the page should be indexed. If yes, remove noindex; if not, consider linking to it less.

Why it matters: The page returns 200 OK but looks like an error or empty page. Search engines may treat it as low quality.

How to fix: Return a real 404/410 for missing content, or add meaningful content to the page.

Why it matters: Temporary redirects tell search engines the move isn't permanent, so they may keep the old URL indexed.

How to fix: If the move is permanent, change it to a 301 or 308 redirect.

Why it matters: A self-referencing canonical helps search engines pick the right URL when parameters or duplicates exist.

How to fix: Add `<link rel="canonical" href="…">` pointing to the page's own preferred URL.

Why it matters: Conflicting canonicals are ignored by search engines, so the page loses its canonical signal entirely.

How to fix: Keep exactly one canonical tag — often a theme and an SEO plugin both add one.

Why it matters: Search engines will ignore a canonical that points to an error or redirect, and may index the wrong URL.

How to fix: Point the canonical to the final, 200-status version of the page.

Why it matters: This sends contradictory signals: 'index that URL instead' while that URL says 'don't index me'.

How to fix: Point the canonical at an indexable page, or remove noindex from the target.

Why it matters: Cross-domain canonicals hand this page's ranking signals to another site. That's correct for syndicated content, but disastrous by mistake.

How to fix: Confirm this is intentional. If not, point the canonical at this page's own URL.

Why it matters: Two hostnames serving the same pages creates site-wide duplicate content and splits link signals.

How to fix: Pick one hostname and 301-redirect the other to it.

Why it matters: Two URLs for the same page split signals unless one redirects or canonicalizes to the other.

How to fix: Redirect one form to the other site-wide, or make sure both canonicalize to the same URL.

Why it matters: Serving both HTTP and HTTPS splits signals across duplicate versions and exposes visitors to insecure pages.

How to fix: Add a site-wide 301 redirect from http:// to https://.

Why it matters: HTTPS is a ranking signal and browsers label HTTP pages 'Not secure', which drives visitors away.

How to fix: Install an SSL certificate and redirect all HTTP traffic to HTTPS.

Why it matters: Browsers show a full-page security warning, and search engines may not crawl the site.

How to fix: Renew or reissue the certificate so it's valid and covers this hostname.

Why it matters: Browsers block or warn about insecure resources on secure pages, which can break layout and trust.

How to fix: Load all images, scripts and styles over https://.

Why it matters: Identical pages compete with each other; search engines choose one and may pick the wrong one.

How to fix: Consolidate the pages, or canonicalize the duplicates to the preferred URL.

Why it matters: Pages with very little text may not fully answer a searcher's question. Word count alone isn't a quality measure — a short page can be perfect for its purpose — so treat this as a prompt to review, not a verdict.

How to fix: If the page is meant to rank, consider adding genuinely useful detail (specs, FAQs, how it works). Never add filler. Short utility pages can be left as they are.

Why it matters: The title is the main headline in search results and a strong relevance signal. Without one, search engines make one up.

How to fix: Write a unique, descriptive title (about 30–60 characters) that says what the page offers.

Why it matters: Titles over ~60 characters are usually cut off in search results, hiding the end of your message.

How to fix: Shorten the title and put the most important words first.

Why it matters: Very short titles miss the chance to describe the page and match what people search for.

How to fix: Expand the title to clearly describe the page (about 30–60 characters).

Why it matters: When many pages share a title, search engines struggle to tell them apart and searchers can't either.

How to fix: Give each page a unique title that reflects its specific content.

Why it matters: The meta description is often shown under your title in search results. A good one can improve click-through rate.

How to fix: Write a unique, compelling summary of the page in about 70–160 characters.

Why it matters: Descriptions over ~160 characters are usually truncated in results.

How to fix: Trim to about 160 characters with the key message first.

Why it matters: Very short descriptions don't give searchers enough reason to click.

How to fix: Expand it to about 70–160 characters describing what the visitor will get.

Why it matters: Identical descriptions make pages look interchangeable in search results.

How to fix: Write a unique description for each page.

Why it matters: The H1 tells visitors and search engines what the page is about at a glance.

How to fix: Add one clear H1 near the top of the page describing its main topic.

Why it matters: Several H1s can blur the page's main topic. It's not an error, but one clear H1 is best practice.

How to fix: Keep one H1 for the main topic and change the others to H2.

Why it matters: A logical heading outline helps accessibility and helps search engines understand the page structure.

How to fix: Use headings in order (H2 under H1, H3 under H2) without skipping levels.

Why it matters: The `<html lang>` attribute helps browsers, screen readers and search engines understand the page language.

How to fix: Add `lang="en"` (or the right language code) to the `<html>` tag.

Why it matters: Without a viewport tag, phones render the desktop layout zoomed out. Google indexes the mobile version of pages.

How to fix: Add `<meta name="viewport" content="width=device-width, initial-scale=1">` to the head.

Why it matters: Open Graph tags control how the page looks when shared on Facebook, LinkedIn, Slack and more. This page has no og:title or og:description.

How to fix: Add og:title and og:description (and a share image) based on the page's real content.

Why it matters: Without og:image, links to this page show no picture when shared on Facebook, LinkedIn, X or Slack, so they look less trustworthy and get fewer clicks.

How to fix: Add a default share image site-wide (1200×630 px), and page-specific images for key pages.

Why it matters: Card tags make shared links show a title, description and image on X.

How to fix: Add twitter:card (and optionally twitter:title/description/image).

Why it matters: Alt text describes images to screen readers and search engines, and helps images appear in image search.

How to fix: Add short, accurate alt text describing each meaningful image. Decorative images can use an empty alt="".

Why it matters: Without dimensions, the page layout shifts as images load, which hurts Cumulative Layout Shift (CLS).

How to fix: Add width and height attributes (or CSS aspect-ratio) to images.

Why it matters: Slow server responses delay everything else on the page and can reduce how much of your site gets crawled.

How to fix: Add caching, optimize database queries, or upgrade hosting. Aim for responses under ~800ms.

Why it matters: Very large HTML documents are slow to download and parse, especially on mobile.

How to fix: Remove inline bloat (large inline scripts, styles or data) and paginate very long lists.

Why it matters: Search engines skip structured data that isn't valid JSON, so the page loses rich-result eligibility.

How to fix: Fix the JSON syntax in the `application/ld+json` script.

Why it matters: Organization markup helps search engines connect your site with your business name, logo and profiles.

How to fix: Add Organization (or LocalBusiness) JSON-LD using only your real, visible business details.

Why it matters: hreflang annotations must be reciprocal; one-way links are ignored.

How to fix: Make sure each alternate page links back to this page with its own hreflang.