SEO Optimization Plan: Remaining Tasks from Search Console Audit

[felixztang]

Current Baseline (3 months, as of Feb 24, 2026)

• 13 total clicks | 686 impressions | 1.9% CTR | Avg position 8.7
• • 115 indexed pages | 97 not indexed
• • • Only 3 external backlinks (all from Reddit)

What's Already Done (commits today)

• Rewrote meta titles/descriptions for all switch pages (migration-urls.ts) to be benefit-focused
• - [x] Updated OG/Twitter meta for ChurchTrac and Tithely switch pages
• - [x] Added BreadcrumbSchema to ChurchTrac and Tithely switch pages
• - [x] Added missing keywords (tithe ai, churchtrac integrations, planning center free alternative)

---

Remaining Tasks (Priority Order)

P0: Fix 14 Broken 404 URLs

These URLs are returning 404 and wasting crawl budget:

1. https://relius.ai/resources/docs/giving/donation-tracking (missing trailing slash - should redirect to /giving/tracking/)
2. 2. https://relius.ai/resources/docs/administration/integrations/ (old URL - redirect to /admin/integrations/)
3. 3. https://relius.ai/resources/docs/giving/tax-receipts/ (old URL - redirect to /giving/receipts/)
4. 4. https://relius.ai/people (should redirect to /resources/docs/people/)
5. 5. https://relius.ai/docs/releases/october/ (old URL path)
6. 6. https://relius.ai/docs/releases/ (old URL path)
7. 7. https://relius.ai/resources/data-cleanup-guide and /resources/data-cleanup-guide/ (duplicate)
8. 8. https://relius.ai/docs/releases (no trailing slash variant)
9. 9. https://relius.ai/$ and https://relius.ai/& (garbage URLs, ignore)
10. 10. https://relius.ai/resources/migration-checklist and /resources/migration-checklist/
        Solution: Since this is a static export on GitHub Pages, create HTML redirect files at each old path or add client-side redirect meta tags in the not-found.tsx with a URL mapping.

P1: Fix 50 "Discovered - Currently Not Indexed" Pages

Most of these are doc pages. Google discovered them but chose not to index them.

Root cause: All 80+ doc pages in the sitemap have the identical lastmod date (2026-02-17) and identical priority (0.5), signaling they may be auto-generated/thin content.

Solutions:

• Stagger lastmod dates in public/sitemap.xml to reflect realistic creation/update times
• - [ ] Vary priority values (getting-started docs should be 0.6, deep reference docs 0.4)
• - [ ] Ensure each doc page has substantial unique content (500+ words), unique H1, and unique meta description
• - [ ] Consider adding noindex to purely navigational doc index pages
• - [ ] Split sitemap into multiple sitemaps (blog-sitemap.xml, docs-sitemap.xml, pages-sitemap.xml)

P2: Add Breadcrumb Schema Sitewide

Currently only 4 pages have breadcrumb structured data. The BreadcrumbSchema component exists.

• Add BreadcrumbSchema to all blog post layouts
• - [ ] Add BreadcrumbSchema to all use-case pages
• - [ ] Add BreadcrumbSchema to all doc pages
• - [ ] Add BreadcrumbSchema to features, pricing, about, contact pages
• - [ ] Add BreadcrumbSchema to Planning Center switch page

P3: Add Page-Specific FAQ Schema

• Add FAQ schema to ChurchTrac switch page (migration-specific FAQs)
• - [ ] Add FAQ schema to Tithely switch page
• - [ ] Add FAQ schema to Planning Center switch page
• - [ ] Add FAQ schema to pricing page

P4: Fix Public Image Filenames

Images in /public/ have non-SEO-friendly names:

• Rename ChatGPT Image Nov 10, 2025, 01_19_37 PM.png -> descriptive name like church-management-illustration.png
• - [ ] Rename all 4 ChatGPT Image files to descriptive, keyword-rich names
• - [ ] Update all references to these images throughout the codebase

P5: Create Content for High-Opportunity Queries

Queries showing impressions but 0 clicks where we're close to page 1:

• "efca competitors alternatives ai" (24 impressions, position 8.2)
• • "church management software ai" (9 impressions, position 10.9)
• • • "church donor data migration" (8 impressions, position 14.9)
• • • • "ai church software" (6 impressions, position 16.8)
• • • • • "planning center free alternative" (2 impressions, position 24)
          Action: Create dedicated blog posts or landing pages targeting these specific queries.

P6: Build External Backlinks

Only 3 external backlinks currently (all Reddit). Need to:

• Submit to church software directories (Capterra, G2, GetApp)
• - [ ] Write guest posts on church leadership blogs
• - [ ] Engage in church tech communities
• - [ ] Promote comparison blog posts for natural link building

Key Metrics to Track

• /switch/churchtrac/ CTR (currently 0% with 97 impressions at position 11.1)
• • /switch/tithely/ CTR (currently 0% with 42 impressions at position 11.1)
• • • Brand query "relius" CTR (currently 1.4% at position 6.1)
• • • • Total indexed pages vs not-indexed ratio
• • • • • Breadcrumb valid items count in Search Console

[felixztang]

Tech Debt Elimination Plan - Status Audit & Actionable Roadmap

Audit Summary (Feb 24, 2026)

Cross-referenced Issue #15 tasks against all merged commits. Here's what's done vs still open.

---

What's Already Been Fixed (Can Be Checked Off)

Task	Fixed In	Status
Meta titles/descriptions for switch pages	989f524 (Feb 24)	Done
OG/Twitter meta for ChurchTrac & Tithely	9b081b9, a8f20cf (Feb 24)	Done
BreadcrumbSchema on ChurchTrac & Tithely	9b081b9, a8f20cf (Feb 24)	Done
Missing keywords added	989f524 (Feb 24)	Done
BreadcrumbSchema on features, AI, pricing, switch, use-cases	04ed13e (Feb 9)	Done
BreadcrumbSchema on about, contact, security, privacy, terms, blog hub, use-case detail, docs layout	fa46a5a (Feb 17)	Done
Fix sitemap dead URLs (removed 7 non-existent /resources/ URLs)	04ed13e (Feb 9)	Done
Expand sitemap from 36 to 114 URLs	fa46a5a (Feb 17)	Done
Block /_next/ in robots.txt	fa46a5a (Feb 17)	Done
5 redirect pages created (docs/releases, resources/data-cleanup-guide, migration-checklist, staff-communication-template)	fa46a5a (Feb 17)	Done
Remove deprecated FAQPage structured data	c7d310c (Feb 12)	Done
Fix footer social links	04ed13e (Feb 9), 8371a78 (Feb 9)	Done

---

What's Still Broken (Remaining Tech Debt)

---

Sprint 1: CRITICAL - Fix Remaining 404s (Do This Week)

Impact: Stop wasting crawl budget. 14 URLs still returning 404 in Search Console.

The Feb 17 commit fixed 5 redirects but several 404 URLs from Search Console remain unfixed. Here's the exact list with what needs to happen:

404 URLs That Still Need Redirect Pages

Old URL (404)	Redirect Target	Fix
/people	/resources/docs/people/	Create app/people/page.tsx with redirect()
/resources/docs/giving/donation-tracking (no trailing slash)	/resources/docs/giving/tracking/	Add redirect logic in the catch-all OR create a dedicated page
/resources/docs/administration/integrations/	/resources/docs/admin/integrations/	Old "administration" prefix needs to map to new "admin" prefix
/resources/docs/giving/tax-receipts/	/resources/docs/giving/receipts/	Old slug "tax-receipts" needs to redirect to "receipts"

Recommended approach: Add a redirect map to the [...slug]/page.tsx catch-all.

Instead of creating individual redirect files, add a REDIRECT_MAP at the top of app/resources/docs/[...slug]/page.tsx:

const REDIRECT_MAP: Record<string, string> = {
  'giving/donation-tracking': '/resources/docs/giving/tracking/',
  'giving/tax-receipts': '/resources/docs/giving/receipts/',
  'administration/integrations': '/resources/docs/admin/integrations/',
};

// In the component, before the notFound() call:
const slugPath = slug.join('/');
if (REDIRECT_MAP[slugPath]) {
  redirect(REDIRECT_MAP[slugPath]);
}

For /people, create app/people/page.tsx:

import { redirect } from "next/navigation";
export default function PeopleRedirect() {
  redirect("/resources/docs/people/");
}

Garbage URLs (No Action Needed)

• /$ and /& - These are garbage URLs from bots. No redirect needed. They'll age out of Search Console.

Acceptance Criteria

• Visiting relius.ai/people/ redirects to /resources/docs/people/
• Visiting relius.ai/resources/docs/giving/donation-tracking redirects to /resources/docs/giving/tracking/
• Visiting relius.ai/resources/docs/administration/integrations/ redirects to /resources/docs/admin/integrations/
• Visiting relius.ai/resources/docs/giving/tax-receipts/ redirects to /resources/docs/giving/receipts/

---

Sprint 2: HIGH PRIORITY - Sitemap & Indexing Quality (Next Week)

Impact: 50 pages "Discovered - currently not indexed" + 2 "Crawled - not indexed"

2A. Stagger Sitemap lastmod Dates

Problem: All 77 doc pages have identical lastmod: 2026-02-17 and identical priority: 0.5. Google sees this as a signal of auto-generated/low-value content.

Fix: Update public/sitemap.xml to:

1. Vary lastmod dates - Use realistic dates based on when content was actually written/updated. Getting Started docs should be earliest (Feb 5-6), later sections should be Feb 11-17.
2. Vary priority values:
   • Getting Started section: 0.6 (high-value entry points)
   • People, Events, Giving: 0.55 (core feature docs)
   • Reference section (shortcuts, API, glossary): 0.4 (low search intent)
   • FAQ, Releases: 0.35

2B. Split Sitemap Into Multiple Files

Why: Google recommends topical sitemaps for large sites. With 114 URLs, splitting helps Google understand content architecture.

Create a sitemap-index.xml and update robots.txt to point to it.

2C. Consider noindex for Thin Doc Pages

Some doc pages in the catch-all route are just "Content Coming Soon" placeholders. These actively hurt SEO.

Action: Audit which doc pages under [...slug] still show placeholder content vs actual content. For placeholders, either add real content (preferred), add noindex meta tag, or remove from sitemap.

Acceptance Criteria

• No two doc pages in the sitemap share the same lastmod date
• Priority values range from 0.35 to 0.6 for doc pages
• Sitemap is split into 3 files with an index
• All placeholder "Coming Soon" doc pages are either filled with content or noindexed

---

Sprint 3: MEDIUM PRIORITY - Image Cleanup & Remaining Schema (Week After)

3A. Rename ChatGPT Image Files

4 images in /public/ have non-descriptive names like ChatGPT Image Nov 10, 2025, 01_19_37 PM.png. After renaming, grep the entire codebase for old filenames and update all references.

3B. Add BreadcrumbSchema to Planning Center Switch Page

File: app/switch/planning-center/page.tsx - same pattern as ChurchTrac/Tithely.

3C. FAQ Schema (Deprioritized)

The Feb 12 commit removed FAQPage structured data because Google deprecated FAQ rich results for non-authoritative sites in 2023. Do NOT re-add FAQ schema.

---

Non-Code Work (Ongoing)

P5: Content Strategy for High-Opportunity Queries

• "efca competitors alternatives ai" (24 imp, pos 8.2)
• "church management software ai" (9 imp, pos 10.9)
• "church donor data migration" (8 imp, pos 14.9)
• "planning center free alternative" (2 imp, pos 24)

P6: External Backlinks

• Submit to Capterra, G2, GetApp
• Engage church tech communities

---

Summary

Sprint	Tasks	Effort	Impact
Sprint 1 (This Week)	Fix 4 remaining 404 redirects	~1 hour	High - stops crawl budget waste
Sprint 2 (Next Week)	Sitemap staggering + split + thin content audit	~3 hours	High - addresses 50 unindexed pages
Sprint 3 (Week After)	Image renames + Planning Center breadcrumbs	~1 hour	Medium - professional polish
Ongoing	Content strategy + backlinks	Ongoing	Long-term growth

[felixztang]

Plan Correction: Verified Issues & Revised Priority Order

After fact-checking the assessment against live production and source code, here's what I verified and the corrected plan.

---

Verified Issues

1. Redirect Mechanism: Client-Side Only (HTTP 200, Not 301) ✅ CONFIRMED

All existing "redirect" pages (e.g. /resources/data-cleanup-guide/, /docs/releases/) use Next.js redirect() from next/navigation, which on a static export (output: "export" in next.config.ts) generates an HTML page that does a client-side redirect. These return HTTP 200 to Google's crawler, not HTTP 301.

Tested live: GET https://relius.ai/resources/data-cleanup-guide/ → Status 200, no Location header.

Google does follow client-side redirects eventually, but treats them as weaker signals than HTTP 301s. On GitHub Pages, true server-side redirects are not possible without an edge layer (Cloudflare, etc.).

Decision needed: Accept client-side redirects as "good enough" for now, or add Cloudflare/edge layer for real 301s.

2. Broken Internal Links in Doc Pages ✅ CONFIRMED

Found multiple broken cross-references within documentation pages that link to slugs that don't exist in docsNavigation:

File	Broken Link	Should Be
app/resources/docs/people/page.tsx	/resources/docs/people/family/	/resources/docs/people/families
app/resources/docs/people/page.tsx	/resources/docs/people/visitor/	/resources/docs/people/visitors
app/resources/docs/admin/page.tsx	/resources/docs/getting-started/roles-permissions	/resources/docs/getting-started/roles

These resolve to 404 on production. A full codebase grep for all href="/resources/docs/..." links should be run against the valid paths in data/docs-navigation.ts to find the complete list.

3. Duplicate Robots Meta on 404 Pages ✅ CONFIRMED

Live 404 pages (e.g. relius.ai/people/) emit two conflicting robots meta tags:

<meta name="robots" content="noindex">
<meta name="robots" content="index, follow">

The noindex comes from Next.js's built-in not-found handling. The index, follow comes from the root app/layout.tsx metadata. These contradict each other.

Fix: Add explicit robots: { index: false, follow: false } to app/not-found.tsx metadata export, or remove the global robots from layout.tsx and set it per-page.

4. Duplicate BreadcrumbList Schema on Switch Pages ✅ CONFIRMED

switch/layout.tsx injects a 2-item BreadcrumbList (Home → Switch), and switch/churchtrac/page.tsx + switch/tithely/page.tsx each inject their own 3-item BreadcrumbList (Home → Switch → ChurchTrac/Tithely).

Result: 2 BreadcrumbList schemas on every switch subpage. Google may pick either one unpredictably.

Fix: Remove BreadcrumbSchema from switch/layout.tsx (since the child pages have more specific breadcrumbs), OR remove from child pages and keep only the layout version.

5. Sitemap URLs All Return 200 ✅ CONFIRMED

Spot-checked multiple sitemap URLs — all return HTTP 200. The sitemap itself is clean. The lastmod/priority uniformity is a quality issue, not a broken-entry issue.

---

Revised Priority Order

Based on verified findings, the corrected sprint order is:

Sprint 1 (This Week): Fix Internal Broken Links + Remaining 404 Redirects

1. Audit all href="/resources/docs/..." links across all doc pages against data/docs-navigation.ts. Fix every mismatched slug (family→families, visitor→visitors, roles-permissions→roles, etc.)
2. Create redirect pages for the 4 remaining Search Console 404s (/people, /resources/docs/giving/donation-tracking, /resources/docs/administration/integrations/, /resources/docs/giving/tax-receipts/)
3. Add REDIRECT_MAP to the [...slug] catch-all so old doc slugs redirect to new ones

Sprint 2 (This Week): Fix Schema & Robots Conflicts

1. Remove duplicate BreadcrumbSchema — delete from switch/layout.tsx, keep the more specific versions in child pages
2. Fix 404 robots conflict — add explicit noindex metadata to not-found.tsx
3. Decide on redirect strategy — document whether client-side redirects are acceptable or if Cloudflare edge is needed for true 301s

Sprint 3 (Next Week): Sitemap Quality

1. Stagger lastmod dates across doc pages
2. Vary priority values by section
3. Consider splitting into multiple sitemaps
4. Audit "Coming Soon" placeholder pages — noindex or fill with content

Sprint 4 (Following Week): Polish

1. Rename ChatGPT image files
2. Add BreadcrumbSchema to Planning Center switch page (after layout duplicate is resolved)
3. Content strategy for high-opportunity queries

[mokashiswapnil]

Solid SEO rescue plan. Your indexing issues are classic thin content and cralw buudget waste. Quick tactical breakdown:

404 Redirects: Use server-side 301 redirects, not client-side meta tags. GitHub Pages supports .htaccess redirects. Create a file mapping old paths:

Redirect 301 /resources/docs/giving/donation-tracking/ /giving/tracking/
Redirect 301 /people/ /resources/docs/people/

Not Indexed Pages: Your sitemap uniformity is killing indexing. Google sees auto-generated content. Solutions:

• Manually edit `sitemap.