SSWConsulting / SSWConsulting/SSW.Website

🔍 SEO - Pages not being indexed

Open
#2,772 4 comments 0 reactions 1 assignee View on GitHub

@Calinator444 is already working on this.

Since Jul 2, 2024.

Dominant language
HTML
Stars
14
Forks
10
Avg merge
13h 51m
Merged PRs (30d)
38

Description

📒📒 Broken into separate PBIs:
#2811
#2812

Based on the email chain:

From: @wicksipedia
Sent: Monday, June 24, 2024 11:20 AM
To: @andrewwaltosssw
Cc: @sethdaily ; SSW Website v3 SSWWebsiteV3@ssw.com.au; @camillars; Jeoffrey Fischer [SSW] JeoffreyFischer@ssw.com.au
Subject: Re: New reasons prevent pages in a sitemap from being indexed on site https://www.ssw.com.au/

Description
Search Console has identified that some pages on our website are not being indexed.

URL
https://search.google.com/u/1/search-console/index?resource_id=https://www.ssw.com.au/&utm_source=wnc_20237597&utm_medium=gamma&utm_campaign=wnc_20237597&utm_content=msg_110624660&hl=en

Solution
Fix the following issues.

Source: Website

  • Alternate page with proper canonical tag - 26,094 pages
  • Page with redirect - 6,543 pages
  • Not found (404) - 2,778 pages
  • Excluded by ‘noindex’ tag - 1,666 pages
  • Duplicate without user-selected canonical - 1,051 pages
  • Soft 404 - 480 pages
  • Blocked by robots.txt - 257 pages
  • Server error (5xx) - 89 pages
  • Blocked due to other 4xx issue - 1 page
  • Blocked due to access forbidden (403) - 1 page

Source: Google systems

  • Crawled - currently not indexed - 36,173 pages
  • Discovered - currently not indexed - 995 pages
  • Duplicate, Google chose different canonical than user - 10 pages

Acceptance Criteria

  • All issues are fixed
  • Reply 'Done' to all emails mentioned in this PBI and @mention the sender with 'Done'"

Screenshots
Image
Figure: 76k pages are not indexed

Image
Figure: List of reasons why pages aren't indexed. Source: Website

Image
Figure: List of reasons why pages aren't indexed. Source: Google systems

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.