Your first URL roast

Screenshot vs URL: when to use each

Use a screenshot when you care about the visual experience — layout, button size, image placement, whitespace, trust signals that only show visually.

Use a URL when you care about copy and messaging — the words on your page, headline strength, benefit clarity, CTA copy, objection handling.

URL roasts analyse the text content of your page. Screenshot roasts analyse what the visitor sees visually. Both score the same result schema, so you can compare results across methods.

Step 1: Switch to URL mode

On the Roast page, click the URL tab (next to the Screenshot tab).

Step 2: Paste your URL

Paste the full URL of your landing page, including https://. PageScorch will fetch the page directly.

URLs that work well:

• Standard HTML landing pages
• Marketing pages with visible copy
• SaaS home pages, sales pages, product pages

URLs that may not work:

• JavaScript-heavy SPAs where all content is rendered client-side after load
• Pages behind a login wall
• Pages that block bots (e.g. aggressive Cloudflare challenges)

If your URL is blocked, see the section below on the manual paste fallback.

Step 3: Submit

Click Analyze URL. PageScorch will:

1. Fetch the URL and extract visible text content
2. Sanitise the content to remove scripts, ads, and navigation noise
3. Send the cleaned content to the AI for conversion analysis
4. Return a score and problems/wins list

When your site blocks the fetcher

Some sites use anti-bot protection (Cloudflare, BrightData, DataDome) that prevents automated fetching. If PageScorch detects this, you'll see a BOT_BLOCK_DETECTED error on the result page.

If you're signed in, you can retry by pasting your page's HTML source manually:

1. Go to your page in a browser
2. Right-click → View Page Source
3. Select all (Cmd+A or Ctrl+A) and copy
4. On the failed roast result page, click Paste HTML manually
5. Paste your page source and submit

PageScorch will process the pasted HTML through the same pipeline as a normal URL roast.

What PageScorch does not fetch

• Content rendered by JavaScript after page load (unless you use the manual paste method with a fully-rendered source)
• Content behind login walls
• Content in iframes

Next step

Once you have your result: Reading your roast result.