In this video· click a step to jump to it
Test recording
georankland — marketing walk + inline signup + broken Supabase verify-email URL captured (founder-side bug)
24,212 ms · 129,292 pixels changed
We built this regression test for georankland.com — it's yours to keep, free.
Take this test with you
This is a real Playwright test, recorded against georankland.com. Claim it into your own workspace and re-run it on every deploy — free.
export async function test(page, baseUrl, screenshotPath, stepLogger) {
const SITE = 'https://georankland.com';
const APP = 'https://app.georankland.com';
let __step = 0;
const shot = async (label) => {
__step++;
const tag = String(__step).padStart(2, '0') + '-' + label;
const p = screenshotPath.replace(/(\.png)?$/, '-' + tag + '.png');
await page.screenshot({ path: p, fullPage: true });
stepLogger.log('shot ' + __step + ': ' + label);
};Checks run
Notes from the demo run
AI-generatedLastest audited GeoRankLand on its launch day by signing up as a new external user. The marketing site is sharp and the value prop is clear: Google Maps grid rank tracking across 25 locations with an AI fix report, free to try. But every signup since launch is stuck — the Supabase verify-email URL in the inbox ships with a U+FFFD (replacement character) where the = should be between token and the hex token. No external user can complete signup today.
- Sharp landing copyh1 "Find exactly where you're losing customers on Google Maps — before your competitors do" frames the pain in one sentence; trust signals (no credit card · 10s results · built for agencies) and stat strip (6-section AI Fix Report / 25 grid points / PDF in 1 click / Free) make the value-of-free instantly legible.
- Right surface, right timeFree tier exposes the 25-point grid + AI fix report — the meat of the product — which is the right wedge for indie SEO consultants evaluating tools.
- BUG: Verify-email URL is malformedThe Supabase confirmation link ships as `?token<U+FFFD>9e408eda...&type=signup` instead of `?token=9e408eda...&type=signup`. The U+FFFD where `=` should be makes Supabase reject every verify with "Verify requires a token or a token hash". The token also appears truncated (54 hex chars vs the 64 a real PKCE token has).
- IMPACT: every external signup is stuckAccount row is created in Supabase, but the user gets the "Account created! Please check your email" banner and the inbox link cannot complete verification. Zero external users can reach the dashboard right now.
- FIXOpen your Supabase project → Authentication → Email Templates → Confirm signup. Delete the body line containing {{ .ConfirmationURL }} and retype it (don't paste the HTML-escaped version — the default template ships HTML-escaped `=` (=) that some Supabase project versions render as U+FFFD on send). Re-save. Test with any plus-aliased Gmail. Same pattern hit StudyHub, Slideshot, EyeCap, PDFOutput launches this week.
- /auth/v1/verify (Supabase)·Returns 400 validation_failed because the malformed token cannot be re-encoded back to a valid PKCE hash.
- /dashboard and authed surface·Inaccessible until the verify-email URL is fixed in the Supabase template.
7 visual changes
Share this run
Proof your app is not AI slop
This test was built for georankland.com — claim it free
One click copies the test and baseline screenshots into your own Lastest workspace. Re-run on every deploy and catch regressions before your users do — free, no card required.