Skip to content

SEO + GEO Improvements — Manual (human action required)

Date: 2026-04-10 Scope: avelia-health.com website Companion doc: 2026-04-10-seo-geo-automated.md — things Claude can implement in the codebase

These items require external accounts, credentials, off-site actions, ongoing human judgment, or content decisions that can't be automated. Each item notes what Claude needs from you to proceed with any codebase work that depends on it.


PRIORITY 1 — One-time setup (Week 1)

1.1 Google Search Console

Status: Blocking — can't measure anything without this. Effort: 30 min Steps:

  1. Go to https://search.google.com/search-console
  2. Add a property for https://avelia-health.com
  3. Choose verification method:
    • Option A (preferred): DNS TXT record — add to your DNS provider
    • Option B: HTML meta tag — paste the verification code into this doc, and Claude will add it to src/layouts/BaseLayout.astro
  4. Once verified, submit the sitemap: https://avelia-health.com/sitemap-index.xml
  5. Also add properties for:
    • https://www.avelia-health.com (if www resolves)
    • https://avelia-health.com/en/ (locale-specific, optional but useful)
    • https://avelia-health.com/de/

What to capture:

  • First-week crawl stats
  • Any URL coverage errors
  • Core Web Vitals field data (may take 28 days to populate)

Claude needs from you: HTML verification meta tag (if Option B) OR confirmation that DNS verification succeeded.


1.2 Bing Webmaster Tools

Status: Important — Bing feeds ChatGPT Search, DuckDuckGo, and Yahoo. Often overlooked. Effort: 15 min Steps:

  1. Go to https://www.bing.com/webmasters
  2. Import your site from Google Search Console (one-click if you just set that up)
  3. Or add manually: verify via XML file, DNS TXT, or meta tag
  4. Submit sitemap: https://avelia-health.com/sitemap-index.xml

Claude needs from you: Verification meta tag if using that method.


1.3 IndexNow API

Status: Nice-to-have. Near-instant indexing for Bing, Yandex, and Seznam. Free. Effort: 30 min Steps:

  1. Go to https://www.indexnow.org/
  2. Generate an API key
  3. Create a file at public/{your-key}.txt containing the key on a single line (Claude can do this once you have the key)
  4. Future: Claude can wire up automatic submission when new content is published via a webhook or deploy script

Claude needs from you: IndexNow API key.


1.4 Social media profiles

Status: Required for Organization schema sameAs array. Critical for entity disambiguation by LLMs. Effort: Depends on whether profiles exist

Profiles to create or collect URLs for:

  • [ ] LinkedIn company page: https://linkedin.com/company/avelia
  • [ ] Twitter / X: https://twitter.com/avelia_health (or similar)
  • [ ] Instagram: https://instagram.com/avelia.health
  • [ ] Mastodon (optional, privacy-friendly): e.g. https://mastodon.social/@avelia
  • [ ] Bluesky: https://bsky.app/profile/avelia.bsky.social
  • [ ] GitHub org (if you publish any open-source code): https://github.com/avelia
  • [ ] YouTube channel (for future product demos)

For each profile:

  • Use consistent branding (logo, colours, tagline)
  • Link back to avelia-health.com in the bio
  • Use the same name (Avelia or Avelia Health) everywhere

Claude needs from you: A list of the URLs once they exist. Paste them into this doc and Claude will update the Organization schema.


1.5 Founder / team LinkedIn profiles

Status: Required for E-E-A-T. Google YMYL rankings weight named, credentialed humans for health content.

For each founder / team member:

  • [ ] LinkedIn URL
  • [ ] Full name
  • [ ] Exact job title
  • [ ] Short bio (2-3 sentences, first-person or third-person — pick one and be consistent)
  • [ ] Profile photo (will be used on About page and author pages)
  • [ ] Relevant credentials (degrees, certifications)

Minimum for SEO impact: Anton Anders + one medical reviewer.

Claude needs from you: A table like:

Name: Anton Anders
Role: Founder & CTO
LinkedIn: https://linkedin.com/in/...
Bio: ...
Photo: /images/team/anton.jpg

Claude will then create /en/team/anton-anders and link it from everywhere an author is mentioned.


1.6 Medical reviewer identity

Status: Critical for YMYL trust. Google devalues unreviewed medical content.

What's needed:

  • [ ] A real medical professional willing to be publicly named as reviewer
  • [ ] Credentials: medical degree, specialty (e.g. "Gynecology & Obstetrics"), licensing body
  • [ ] Affiliation: hospital, clinic, university
  • [ ] A written agreement that they review specific guides before publication
  • [ ] A review process: each guide tagged with reviewer name + review date

Claude needs from you: Once identified, paste the reviewer's name, credentials, affiliation, and LinkedIn (if any) into this doc. Claude will add a reviewer_* field to the CMS guide model and surface it on every guide.


Status: Required for accurate Organization schema and legal compliance. Question: Is "Avelia" a registered legal entity yet? If so:

  • [ ] Legal name (e.g. "Avelia GmbH")
  • [ ] Registration number (HRB number for German GmbH)
  • [ ] VAT ID
  • [ ] Registered address (for Impressum + schema address)
  • [ ] Managing director name

Claude needs from you: These fields for the Organization schema enrichment.


PRIORITY 2 — Content strategy decisions (Week 2-4)

2.1 Content velocity commitment

Status: Strategy decision. The plan assumes 1 guide + 2 blog posts per week.

Decisions needed:

  • [ ] Who writes? (You, medical reviewer, freelancers, a mix?)
  • [ ] Budget for writers / editors?
  • [ ] Tooling: Cockpit CMS is set up, but is the editorial workflow defined?
  • [ ] Legal review for medical claims?
  • [ ] Fact-checking process?

Alternative: Lower cadence (1 post/week total) is fine if quality is higher. Google rewards quality over quantity.

Claude can help with: Writing first drafts if you provide topic briefs. Flag when a claim needs citation or medical review.


2.2 Topic research — seed queries

Status: Strategy decision. Need a list of target long-tail queries to write against.

How to generate the list (manual):

  1. Brainstorm 10 core questions your ideal user would ask:
    • "Is Flo safe for fertility tracking in Germany?"
    • "What's the best private period tracker in 2026?"
    • "How do I track cycles without giving data to big tech?"
    • "Can my partner see my cycle tracking data?"
    • etc.
  2. For each question, use Google + People Also Ask + Google Suggest to find related queries
  3. Also check:
  4. Create a spreadsheet: query | search volume estimate | intent (info / navigational / transactional) | target page

Claude can help with: Drafting articles for a given query. Cannot get real-time search volume data.


2.3 Blog / guide content calendar

Status: Ownership decision.

Starter calendar (first 12 weeks):

WeekBlog (2)Guide (1)
1"Why we left Flo" + "What zero-knowledge means""Your first IVF cycle: a week-by-week guide"
2"Cycle tracking apps and your rights" + "Safe Mode explained""Basal body temperature: the complete guide"
3......

You fill in the rest based on your research from 2.2.

Claude can help with: Drafts once you provide the topic list.


2.4 Pillar page content

Status: Each of the 7 stage pillar pages needs real content (infrastructure Claude can build, writing is ongoing).

Per pillar (500-1,500 words):

  • What happens in this stage (medical + emotional overview)
  • Common challenges
  • Key decisions and their timing
  • Red flags that need medical attention
  • How Avelia supports this stage

Claude can help with: Drafting. You or the medical reviewer should fact-check and approve.


PRIORITY 3 — Ongoing operations

3.1 Weekly GEO cite-check

Status: Manual, ongoing. No established tools exist yet.

Process (15 min/week):

  1. Open ChatGPT, Claude, Perplexity, and Google (AI Overviews)
  2. Run these canonical queries:
    • "What is a zero-knowledge period tracker?"
    • "Is Avelia safe for tracking fertility in Germany?"
    • "Best private fertility app 2026"
    • "End-to-end encrypted period tracker"
    • "How do I hide my period tracker from my partner?"
  3. Log results in a spreadsheet:
DateQueryChatGPT cites Avelia?Claude?Perplexity?Google AIO?Notes
2026-04-10"..."NoNoNoNoFirst baseline
  1. Watch for improvement as GEO changes land
  2. If Avelia is cited, screenshot and save

Claude can help with: Generating the canonical query list. Can't run the queries themselves (no LLM-of-LLMs access).


3.2 Weekly Google Search Console review

Status: Ongoing.

Every Monday (10 min):

  • Check Coverage report for new errors
  • Check Core Web Vitals report (field data trailing 28 days)
  • Check Performance report:
    • Top queries (sort by impressions, then CTR)
    • Top pages
    • Any query with high impressions + low CTR → rewrite title tag
  • Check Enhancements → any structured data errors

3.3 Monthly content audit

Status: Ongoing.

First Monday of each month (1 hour):

  • Which pages have zero clicks despite being indexed? (Either improve or deindex.)
  • Which pages have high CTR but low impressions? (Target similar content.)
  • Which pages have high impressions but no clicks? (Rewrite title + meta description.)
  • Which pages have highest engagement in Matomo? (Double down on similar topics.)

3.4 Quarterly GEO audit

Status: Ongoing.

Every 3 months:

  • Re-run the LLM cite-check with updated queries
  • Check if competitors (Flo, Clue, Stardust) now appear in queries where Avelia doesn't
  • Check Avelia's llms.txt and llms-full.txt are still accurate
  • Refresh facts (dates, versions, prices) across static content
  • Check if new LLM crawlers emerged — update robots.txt allowlist

PRIORITY 4 — Nice-to-haves

Status: Optional but high-impact for traditional SEO.

Where to seek backlinks:

  • [ ] FemTech industry publications (e.g. Femtech Insider, Femtech Focus)
  • [ ] Privacy-focused outlets (Mozilla Privacy Not Included, EFF, Signal blog)
  • [ ] German health tech directories (Gesundheit.de, etc.)
  • [ ] Healthcare partner websites (clinics, midwives who distribute Avelia licenses)
  • [ ] Open-source cryptography community (if any components are open-sourced)

Process:

  1. Draft a 2-paragraph pitch
  2. Identify 5-10 target sites
  3. Reach out one at a time with personalised messaging
  4. Track in a spreadsheet

Claude can help with: Drafting pitch text. Cannot send emails.


4.2 Podcast / interview appearances

Status: Optional.

  • Privacy-focused podcasts (Opt Out, Privacy International)
  • FemTech podcasts
  • German startup podcasts
  • Tech ethics podcasts

Each appearance = at least one high-authority backlink plus entity signal for LLMs.


4.3 Scholarly citations

Status: Long-term.

If Avelia publishes any whitepapers or technical documentation (e.g. detailed Argon2id implementation notes, Safe Mode cryptographic analysis), consider:

  • Posting to arXiv
  • Submitting to privacy / cryptography conferences
  • Publishing on GitHub with a public repo

Scholarly citations are the strongest possible E-E-A-T signal.


4.4 Paid tools (optional, ~€100-300/mo)

Status: Optional. All items above can be done without paid tools.

If budget allows, consider:

  • Ahrefs or Semrush — keyword research, backlink monitoring, SERP tracking (~€100-200/mo)
  • Screaming Frog SEO Spider — one-time license ~€200/year, runs locally
  • Wappalyzer Pro — competitor tech stack analysis

Skip these if budget is tight; free alternatives work.


Handoff tracking

When you complete an item, update this doc with:

  • Date completed
  • Any URLs, credentials, or IDs Claude needs to proceed with dependent codebase work
  • Blockers or decisions deferred

Example:

- [x] 1.1 Google Search Console — 2026-04-12 — verified via DNS TXT record, property at https://search.google.com/search-console?resource_id=...
- [ ] 1.4 Social profiles — deferred until logo finalised

Summary of information Claude needs to unblock codebase work

When you have any of these, paste them into this doc and tag Claude:

  1. Google Search Console verification code (if HTML method) → Claude adds to BaseLayout.astro
  2. Bing Webmaster verification code (if HTML method) → Claude adds to BaseLayout.astro
  3. IndexNow API key → Claude creates public/{key}.txt
  4. Social profile URLs → Claude updates Organization schema sameAs array
  5. Founder info (name, role, LinkedIn, bio, photo) → Claude creates /en/team/[slug] pages
  6. Medical reviewer (name, credentials, affiliation) → Claude adds CMS fields + UI on guides
  7. Legal entity details (name, address, HRB number) → Claude updates Organization schema + Impressum
  8. Content briefs (topic, target query, key points) → Claude drafts articles

Private by design.