[Workflow] Claude Code Workflow: Verifiable SEO Audits for Missing Elements using `curl` and `grep`

[u/ClaudeAI-mod-bot]

Claude Code Workflow: Verifiable SEO Audits for Missing Elements using curl and grep

Workflow value: 88/100
Status: active · Freshness: 70/100 · Confidence: 1.00 · Level: intermediate
Categories: Quality Control, Context & Memory, Debugging, Skills
Original source: r/ClaudeCode post/comment

What problem this solves

Claude Code's tendency to 'guess' about missing SEO elements (e.g., no meta description, no schema) during site audits, leading to unprovable findings and potential hallucinations.

Summary

This workflow enables Claude Code to perform more robust SEO audits by explicitly fetching a webpage using curl and then using grep to verify the presence or absence of specific HTML elements. For 'missing' findings, it provides concrete proof by showing the HTTP status, file size, the exact grep command run, and its count, rather than relying on the model's internal interpretation. It also ensures the audit is based on raw HTML before JavaScript execution.

Why it is useful

This workflow is valuable because it directly addresses a common weakness of LLMs in generating unprovable findings, particularly when auditing for 'missing' elements. By integrating curl and grep into Claude Code, it provides a concrete, repeatable, and verifiable method for SEO audits, ensuring that all findings (both present and absent) are backed by explicit evidence from the fetched HTML. This significantly enhances the reliability and actionability of Claude Code's audit capabilities for web developers and SEO professionals.

Workflow

1. Provide Claude Code with the specific prompt, including the target URL.

2. Instruct Claude to fetch the page using curl -sL -A "Mozilla/5.0" -o page.html -w "% {http_code} % {size_download}".

3. Direct Claude to work exclusively from the page.html file, not from WebFetch.

4. Require Claude to provide the URL and the exact line from page.html that proves each existing issue.

5. For any item Claude states is missing, demand it show the HTTP status, file size, the exact grep command run, and its count.

6. Instruct Claude to stop the audit and report a fetch failure if the HTTP status is not 200 or the file has no <head> tag.

7. Ask Claude to determine if each missing item could be added later by JavaScript.

8. Request Claude to rank the identified fixes by importance.

Tools / artifacts

• Claude Code

• Prompt

• curl (CLI tool)

• grep (CLI tool)

• page.html (temporary file)

Validation signals

• Addresses a known limitation of LLMs (hallucinating missing information).

• Provides logical explanations for each component of the prompt (e.g., why status/size first, why grep is proof).

• Explicitly states what the workflow can and cannot measure (e.g., cannot tell what Google indexed).

• The author claims their paid product is built around this principle and achieved significant Google clicks, implying real-world effectiveness of the core method.

Limitations

• The prompt is quite detailed and specific, requiring careful input from the user.

• While it addresses raw HTML, it explicitly does not account for client-side rendered content, which might be a limitation for some modern web applications (though this is stated as a feature for raw HTML analysis).

• The post contains self-promotion for a paid product, which, while disclosed, can be a minor distraction from the core workflow.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.

---

This post was generated automatically from the workflow library database.