Skip to content

Growth: verify 80 index candidates, expand search demand safely, and measure organic conversions #37

Open

Description

@appdevelopsk

Background (2026-11-05)

  • Site provides 223 tools in 17 active UI locales.
  • site/scripts/report-index-policy.ts explicitly distinguishes 80 intended index URLs from actual GSC coverage and notes thousands of deliberate noindex tool-locale variants. Do not mass-remove noindex without live evidence.
  • site/src/app/sitemap.ts uses indexableLocalesFor() to keep the sitemap aligned with index policy and produces hreflang alternates for eligible locales.
  • site/src/app/robots.ts allows crawling and advertises sitemap.
  • site/scripts/audit-seo.ts, site/scripts/indexnow.ts, site/package.json already have SEO audits, IndexNow, post-build metadata checks, and GA4 calculate reporting. Avoid duplicate implementations.
  • Public /en/tools includes overlapping intent WPM Typing Speed Test and Typing Speed Test; assess differentiation before canonical changes.
  • Site URL defaults to example.pages.dev if NEXT_PUBLIC_SITE_URL absent: verify production config and fail build on invalid production canonical host only if not already covered.

Execution tasks

  • Export last 28 and preceding 28 days GSC by page/query/country/device (Google) plus Bing equivalent. Record clicks, impressions, CTR, average position; segment by locale.
  • Run npm run audit:index-policy -- --json, npm run audit:seo, npm run audit:i18n, npm run validate, npm run typecheck, npm run test, npm run build locally. GitHub Actions must not be used.
  • Compare 80 candidate URLs to live sitemap, meta robots, canonical, 200 status, hreflang reciprocity and GSC index coverage. Do not interpret tool fetch failure as live 404.
  • Identify top 10 URLs by high impressions / low CTR, rewrite unique titles, descriptions, examples, FAQ and related-tool links without altering calculation logic.
  • Compare WPM tools and any other duplicated keyword clusters. Keep both if meaningfully distinct, else propose canonical/redirect after measuring actual usage.
  • Validate cross-link funnels: /en/tools JSON formatter, CSV JSON converter, regex tester, image resizer into relevant currently available /en/software products; no coming-soon payment promises.
  • Verify GA4 events calculate, copy_result, preset_click and software_open or equivalent; register tool_slug / locale / category dimensions and report organic landing -> tool usage -> software visit conversion.
  • When proven locale-query demand exists, add a small documented INDEX_EXCEPTIONS batch (e.g. 5–10 URL/locale pairs) with explicit rollback and 28-day evaluation; do not enable all 17 languages indiscriminately.
  • Post-deploy submit only valid changed canonical URLs via existing IndexNow implementation. External store/publication/deployment is owner-handled.

Acceptance criteria

  • Evidence table with baseline 28-day GSC + Bing metrics, per URL actionable changes, repo commit refs and local command outputs.
  • No broken canonical/hreflang/noindex/sitemap consistency or increased thin-content indexing.
  • Track changes over the next 28 days versus baseline; no unsubstantiated traffic lift claims.

Status: audit/task definition; no source edits or production deploy yet.

Activity

  1. appdevelopsk commented on Nov 11, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-11 implementation: Draft PR #47 adds fail-early prebuild validation for NEXT_PUBLIC_SITE_URL, rejecting example.pages.dev / preview hosts / malformed origin before canonical/sitemap generation. Standalone Node node --test locally passed 12/12 for equivalent authored source. Full checkout build and production env unverified; Draft pending manual npm ci, typecheck, build and site canonical checks. Existing PR #46 covers new tool journeys; do not reimplement or infer user growth from source changes.

  2. appdevelopsk commented on Nov 11, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-11 correction to previous comment: Toolify journeys PR #46 is now MERGED into repository main (not evidence of production deployment). Canonical-domain gate PR #47 became stale after main advanced, so the same two files were copied without content changes onto current main as Draft PR #48; package.json prebuild was reapplied to the latest main to retain the journeys. Old #47 CLOSED unmerged. PR #48 native complete checkout/Next build and deployed-environment check still pending; keep Draft.

  3. appdevelopsk commented on Nov 11, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-11 12:54 JST verified real CI source/step logs on PR #48. Earlier CI run 42941114377 successfully completed checkout, npm ci, TypeScript, i18n, SEO audit and 203/203 Vitest tests but failed Production build because workflow set NEXT_PUBLIC_SITE_URL=https://example.pages.dev, correctly rejected by new canonical safety checker. Fixed .github/workflows/ci.yml on #48 (commits 71ae785, ec128dc) to set job-level HTTPS apex for both production build and Lighthouse server. New run 42956106878 started, not yet complete at last check; production Pages env/deployment unchanged.

  4. appdevelopsk commented on Nov 11, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-11 latest status correction: canonical-origin and CI regression PR #48 is MERGED INTO main (squash commit 9d9d72c1c4a853fe98a7f0a1d966aeb0cadfec9a). Verified CI on exact PR head fcee4bd, workflow run 42956510545, completed success: npm ci, TypeScript, i18n, SEO audit, canonical origin regression, unit tests, Next.js production build, Lighthouse all passed. Post-merge main readback confirms exact guard blob SHA 3dee63f063971d13f35dd5a30dcbbe9df541cd65 and updated workflow e3f76a8d10bc210387946527faec375d7f5df3e6. This proves merged source and CI only; Cloudflare Pages actual deployed SHA, runtime env, public canonical/hreflang and traffic uplift are NOT verified. Do not close production verification tasks based solely on green CI.

  5. appdevelopsk commented on Nov 15, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-15 concrete implementation — limited index trial

    Draft PR #96 adds only four potential indexed URLs: /en and /ja versions of the actual interactive image-resizer and csv-json-converter. Both tools already have original actionable English content, localized text and homepage journey links. The change reuses the existing canonical/hreflang/sitemap/indexability policy and adds an en/ja-only regression test. Not merged; not live. No full test/build has run and no Github Actions were started.

    Before merge: run cd site && npx vitest run src/lib/tools/registry.test.ts && npm run validate && npm run build; inspect built HTML, 4 canonical URLs, sitemap and noindex non-en/ja variants. Verify public deploy SHA and Google indexing per exact URL, then compare GSC impressions/clicks for 7/14/28 days to unchanged control pages. No mass reindex, no traffic guarantee.

    Evidence context: GSC 2026-11-10–12 opportunities returned no candidates for Toolify365; 2026-11-14 five-business audit reports 1 impression / 1 click in its 28-day Google Search Console window (small sample, not all traffic).

  6. appdevelopsk commented on Nov 15, 2026

    @appdevelopsk
    OwnerAuthor

    2026-11-15 index-quality trial source MERGED; live release still unverified

    PR #96 merged as b14a8c94735d4261f9541cf7e6462e438db02a27 after green GitHub Actions CI (TypeScript, i18n, SEO tests, unit tests, production build and Lighthouse). Only four new search-eligible pages (image-resizer/csv-json-converter, en/ja) are authorized. CSV quoting/duplicate & mismatched columns now fail closed; RFC4180 and MDN sources added. Verify the actual published SHA, exact HTML meta robots/canonical/hreflang/sitemap on those four URLs, and unchanged noindex for non-en/ja variants. Measure 7/14/28-day finalized GSC clicks, qualified tool use, and credible organic referrals before claiming growth.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions