Skip to content

feat: make the anonymous one-page check a clickable CTA on the methodology page - #90

Merged
nish3451 merged 1 commit into
mainfrom
seo-fix-kit/lane1-methodology-check-cta-2
Aug 10, 2026
Merged

nish3451 merged 1 commit into
mainfrom
seo-fix-kit/lane1-methodology-check-cta-2

Conversation

@nish3451

Copy link
Copy Markdown
Owner

What

The /methodology page listed the anonymous one-page check as plain text (at https://seofixkit.com/check:). This turns it into a real clickable CTA:

  1. The /check URL in the "What is live today" list item is now an <a href> link.
  2. Added a primary Check one page now CTA button below the list, styled with the same .cta treatment the demo page uses (added the missing .cta rule to publicProductPageHtml's CSS).
  3. Covers both render paths — the Worker and the local Express server both import methodologyHtml from worker/routes/pages.js.

Tests

  • npm run test:public-pages — 7 pass (added assertions that the URL is a real link and the CTA exists)
  • node --test scripts/live-promise-spot-check.test.mjs — 14 pass (added a live spot-check expectation for href=.../check on /methodology)
  • node --test worker/index.test.mjs — 10 pass

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.

@coderabbitai

coderabbitai Bot commented Aug 10, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@nish3451, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 35 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 9c4104bb-4cd2-4863-b5cd-399df07769d6

📥 Commits

Reviewing files that changed from the base of the PR and between c3ce4a0 and 5fb90cb.

📒 Files selected for processing (3)
  • scripts/live-promise-spot-check.mjs
  • worker/routes/pages.js
  • worker/routes/pages.test.mjs

Comment @coderabbitai help to get the list of available commands.

@nish3451
nish3451 merged commit dbb088d into main Aug 10, 2026
2 checks passed
nish3451 added a commit that referenced this pull request Aug 12, 2026
…ext (#108)

The scout item (plain-text /check on /methodology) was already fixed by #90,
but no test failed if a plain-text mention regressed back in. Add a guard
asserting every /check mention on the methodology page is a link href or a
link's anchor text.
nish3451 added a commit that referenced this pull request Aug 14, 2026
…n — /check free-entry surface live-stale, window must not start (#134)

`npm run audit:live-promise` fails on 9 of 16 surfaces against the
deployed site (pre-#85/#88/#90/#100/#107 copy: missing no-storage
disclosure on /check, missing footer terms/privacy links on
/demo /methodology /packages, missing /check cross-links on
/support /terms /privacy, 422-vs-400 on non-http scheme, www
static asset 200-vs-301). Root cause is the fleet release deploying a
stale Worker + assets bundle on 2026-08-13 22:40 (its log says "No
updated asset files to upload" while recording index-Dd3Lei8e.js as
the marker; live serves the older index-DX7O9nYF.js). Repo source is
green (npm run check + offline spot-check lock pass); this is deploy
machinery, not copy drift. The experiment log now carries the dated
precondition note so the founder does not start the seven-day window
against a broken /check, plus the resume condition (re-verify after a
release that actually swaps the live Worker).

Co-authored-by: minimax-vps-lane1 <minimax-vps@nish.fleet>
Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant