Remaining SEO Findings

Last reviewed: 2026-06-01

This file captures the SEO issues that still remain after the recent cleanup work. The earlier high-value fixes for canonical URLs, sitemap quality, thin-page removal, page-level descriptions, and internal linking have already been addressed.

Ranked Findings

1. Add business schema and machine-readable trust signals

Impact: Medium to high

What remains:

  • There is no LocalBusiness, Organization, PostalAddress, telephone, or sameAs markup in the project.
  • The site currently relies on generic WebSite and WebPage schema generated by the SEO tag output.

Why it matters:

  • This is the clearest remaining gap for local relevance and business identity.
  • The Perth landing page would benefit from stronger location and entity signals.

Evidence:

  • Repository search found no matches for LocalBusiness, Organization, PostalAddress, sameAs, or telephone in source or generated files.
  • Relevant page: cloud-consulting-services-perth.md

Recommended next action:

  • Add business-level structured data for the company.
  • Include business name, URL, service area, and any real public contact or social profile details you want exposed.
  • If you want to push local intent harder, add location cues carefully on the Perth page without overdoing it.

2. Add social preview metadata and a share image

Impact: Medium

What remains:

  • There is no og:image or twitter:image anywhere in the repository or generated output.

Why it matters:

  • Search and social sharing are stronger when pages have a proper preview image.
  • This is especially useful for client sharing, social links, and richer branded previews.

Evidence:

  • Repository search found no matches for og:image or twitter:image.

Recommended next action:

  • Create a default social card image for the site.
  • Wire it into the layout or config so core pages get a consistent preview.
  • Optionally override it for key landing pages later.

3. Improve the 404 page SEO handling

Impact: Medium

What remains:

  • The 404 page still inherits the generic site description.
  • The generated 404 page has a canonical URL but no noindex handling.
  • The 404 page headline and metadata are not specific to the error page.

Why it matters:

  • A 404 page should not compete as a normal landing page in search.
  • Even though this is not as important as your main landing pages, it is still a cleanup item worth doing.

Evidence:

  • Source file: 404.html
  • Generated file: _site/404.html
  • The generated output still shows the generic description and no noindex signal.

Recommended next action:

  • Add 404-specific front matter such as a title and description.
  • Add robots: noindex handling if supported by your SEO setup or layout logic.
  • Keep the page useful for users, but treat it as a non-index target.

External Checks Still Worth Doing

These are not repository-only defects, but they should still be reviewed in the future.

4. Validate real performance and Core Web Vitals in production

Impact: Medium

What remains:

  • This review was repository-based, not a live performance audit.
  • Real-world speed, layout stability, and interaction performance still need production testing.

Recommended next action:

  • Run Lighthouse and PageSpeed Insights against the live site.
  • Check mobile separately from desktop.
  • Review any render-blocking or third-party impact from analytics scripts.

5. Validate indexing and coverage in Google Search Console

Impact: Medium

What remains:

  • Repository checks cannot confirm index status, coverage issues, exclusions, or search query performance.

Recommended next action:

  • Review Search Console coverage, page indexing, and enhancement reports.
  • Check which pages are actually being indexed and whether impressions align with the target service pages.

6. Confirm preferred-host and redirect behavior at the edge

Impact: Medium

What remains:

  • The site now outputs absolute canonicals for https://raydentech.net, but this review did not verify live redirect behavior for alternate hostnames or protocols.

Recommended next action:

  • Confirm live redirects for:
    • http to https
    • www to non-www or vice versa, depending on your chosen preference
  • Make sure the canonical host, CNAME setup, and redirect behavior all agree.

Summary

The major structural SEO issues are no longer the problem. The remaining work is now mostly about:

  • stronger entity and local trust signals
  • better social sharing metadata
  • tidying the 404 page
  • validating live production behavior and search performance