Lighthouse-MD

Just spun up the product page. Lighthouse-MD has been live at lighthouse-md.com for about two weeks. Today is when I am setting up the distribution side of the house, so here is what shipped this week on the record.

## What the tool is

A free converter. Paste a URL, get back a CLAUDE.md fix brief for Claude Code with every failing Lighthouse audit, the actual offender list per audit, prescriptive fixes, and a "currently passing, do not break" section so the agent does not regress accessibility while chasing perf. Same converter ships as a Chrome extension. No signup, no API key, no plans to monetize.

## What shipped this week

Two perf rounds on the homepage itself. Cleared render-blocking-insight and forced-reflow-insight. TBT went 100ms to 30ms. CLS went 0.007 to 0. Site sits at Lighthouse perf 90 mobile now. (Yes, the perf tool's own perf score is the most embarrassing kind of regression. It is fine now.)

16 audit explainer pages prepped for dev.to with canonical_url pointing back. Drips Tue + Fri for 8 weeks starting next Tuesday. SEO credit stays on lighthouse-md.com.

Chrome Web Store listing rewrite. Title bumped to include "Lighthouse" (highest-search keyword). 5 screenshots instead of 2. v0.2.1 zip submitted for review. Generated a fresh 1400x560 marquee promo tile via headless Chrome.

3 awesome-list PRs opened today: awesome-wpo, awesome-seo, best-chrome-extensions. Dofollow backlinks from DA-90 repos compound forever. 1 of 4 (awesome-claude-code) is blocked because their README is mid-rebuild.

Show HN is scheduled for Tuesday morning. Title is "Show HN: Turn a Lighthouse audit into a CLAUDE.md brief for Claude Code." OP comment drafted, pre-launch checklist armed.

## What is next

- Tuesday: Show HN goes up, first dev.to drip (LCP), IndieHackers community post lands the same day

- Thursday: standalone announcement post on dev.to

- Friday: FCP audit on dev.to

- Next 7 weeks: drip continues, awesome-list PR follow-ups, newsletter pitches to Smashing, JS Weekly, Frontend Focus, Bytes

Open to any takes. Especially curious if anyone here has data on dev.to canonical SEO credit when the dev.to post outranks the original on Google. Hunch is I will know in 6 weeks but if you have direct data save me the wait.