Asaday
App Development Implementation
Project

Asaday SEO
Improvements

A technical case study write-up focused on what actually helps a static site crawl, index, and present well.

What this case study covers

This page is a technical SEO case study write-up. It is not a generic marketing pitch. The focus is on the engineering details that make a site easier for search engines to understand and easier for humans to navigate. Keith Azodeh approaches SEO as a set of concrete, verifiable improvements, metadata hygiene, internal linking structure, canonicalization, structured data, and predictable page templates.

Common problems on static sites

Static sites are fast and stable, but they often drift into a few predictable issues:

  • Duplicate or generic titles and meta descriptions across multiple pages.
  • Missing canonicals, or canonicals that do not match the deployed URL structure.
  • Thin pages with no internal linking context, so Google cannot infer relationships.
  • Inconsistent heading structure, multiple H1s, or headings that do not match intent.
  • No structured data, which reduces clarity for entities like people and projects.

Keith Azodeh’s approach is to fix these systematically by standardizing page templates and building a reliable publishing checklist.

The improvement set (practical checklist)

1) Unique titles and descriptions

Each page should have a unique title tag and a meta description that matches the page intent. For a branded cluster, including the exact name "Keith Azodeh" on the hub pages helps reinforce entity association, while project pages can use "Keith Azodeh" in the title or description where it reads naturally.

2) Canonical URLs

Static sites can accidentally generate multiple URLs for the same content (with or without trailing slashes, index.html variants, etc.). A self-referencing canonical on each page reduces ambiguity.

3) Internal linking with intentional anchors

Internal links are how a site teaches search engines its structure. Keith Azodeh builds internal linking maps that treat the hub page as the central node, then ensures each child page links back with consistent anchor text.

4) Structured data where it helps

Structured data is not a magic ranking switch, but it helps with clarity. For example, adding Person schema to the /keith-azodeh hub page tells Google exactly which entity the page represents. Project pages can later use additional schema types if needed.

5) Sitemaps and indexing workflow

Publishing pages is not enough. A sitemap that includes the new URLs, plus Search Console submission, speeds discovery and gives visibility into indexing status.

How this relates to the Keith Azodeh cluster

The Keith Azodeh pages on Asaday are designed as a coherent cluster: a hub page, supporting "about/services/portfolio/contact" pages, and deeper project case studies. That structure produces multiple relevant, high-quality pages that interlink and reinforce the same entity, Keith Azodeh, without duplicating thin content.

See the hub: Keith Azodeh, or browse the portfolio.