/ Is Vibed
$ npx is-vibed [domain]
wordpress.com Rescan

No builder fingerprint found

Nothing in the page, the bundle or public DNS names a website builder. That is not proof it was hand-written — Cursor, Claude Code and Copilot leave no trace at all.

100/ 100 finish
Prompt to improve nothing left to clean up · 0 scored findings · 833 words in initial HTML
AttributionMarks the builder left behind clear
DefaultsScaffold settings never changed clear
FinishProduction basics not yet done clear
SafetySecrets and data access clear

Prompt to improve Open as text
You are working on the codebase behind wordpress.com.

An external scan of the deployed site found the tells listed below — the specific things that make it read as assembled by a website builder rather than built. Fix them in the order given. Each item names the evidence observed on the live page, so you can confirm the problem before you change anything.

Rules for this task:
- Do not redesign the site. Change only what each item asks for.
- Do not change any URL, route or page title beyond what an item explicitly requires.
- If an item does not match what you find in the code, say so and skip it rather than inventing a change.
- Work through the list top to bottom and report what you changed for each.

## Scaffold defaults still in place

### 1. A generator tag names the framework or CMS
Observed on the live site: WordPress.com

Noted, not scored: the page advertises WordPress.com. A static-site generator or CMS says nothing about whether a person or a model wrote the code. Remove the tag if you would rather not publish your stack, but it costs you nothing here.

## Placeholder and filler copy

### 2. Navigation links that go nowhere
Observed on the live site: 3 links with href="#"

Fix the dead navigation: 3 links with href="#". Either point each one at a real route or remove it. A nav bar where half the items do nothing is the fastest way a visitor concludes nothing behind the landing page is real.

### 3. Generic launch-copy vocabulary
Observed on the live site: "seamless" ×1 · "seamlessly" ×1

Rewrite the marketing copy in concrete terms. It currently leans on filler that says nothing specific ("seamless" ×1, "seamlessly" ×1). Replace each claim with what the product actually does, a number, or a named use case. Do not substitute different superlatives.

## When you are done

Re-run the checks yourself before reporting: fetch the deployed page with curl and confirm the markers above are gone from the HTML, that unknown paths return 404, and that `/robots.txt` and `/sitemap.xml` answer 200. Then summarise anything you deliberately did not change and why.

Findings

Nothing scored against this site.

A generator tag names the framework or CMSWordPress.com noted
Navigation links that go nowhere3 links with href="#" noted
Generic launch-copy vocabulary"seamless" ×1 · "seamlessly" ×1 noted