DevAwesomeOpen a tool

Turn raw SEO exports into inputs you can review and reuse.

Load a local export, map its columns, review conflicts or exclusions, and hand off a checked result. Everything runs in your browser.

Prepare a keyword import Build a crawl list
01
Prepare a keyword import

Map columns → find conflicting duplicates → choose a resolution → export the reviewed file

02
Build a clean crawl list

Extract URLs → define scope → inspect exclusions → export targets and rejection reasons

Portable recipes + run manifestsReuse the rules, then bind one input and output with private SHA-256 receipts.
Start with a real job

Two workbenches that leave you with a checked file.

Each workflow keeps the source local, shows the rows that need a decision, and exports both the usable result and the evidence behind it.

Keyword importCSV · TSV · TXT

Clean the file without hiding conflicting metrics.

  1. MapFind keyword, volume, intent, language, and the columns you need to retain.
  2. ReviewSee duplicate keywords whose extra columns disagree. Choose first, last, merge, or manual review.
  3. ExportDownload the reviewed table, a reusable recipe, and an optional run manifest.
Prepare a keyword import
After the export

Import the reviewed list into a workspace, organize it, and add fresh metrics only when you need them.

Continue in Contextter's Keyword Database
Crawl inputXML · CSV · TSV · TXT

Build a crawl plan, not just a shorter URL list.

  1. ScopeChoose host, subdomains, protocol, include rules, exclusions, and resource handling.
  2. ReviewSeparate crawlable pages, robots blocks, resources, invalid URLs, and manual checks.
  3. ExportDownload crawl targets and rejected URLs with the exact reason for each decision.
Build a clean crawl list
When the list is ready

Run a live crawl to inspect status codes, indexability, internal links, and technical issues across the site.

Run the site in Contextter Site Audit

DevAwesome and Contextter are operated by Matthias Ramahi. These links connect related workflow steps and are not independent recommendations.

Two more jobs, when the input is evidence or a protocol message.

The first two workbenches prepare data. These two help explain a technical result.

All workflows
Debug indexabilityPaste headers, rendered head markup, and robots.txt. Extract the signals before reading the verdict.Validate an MCP messageChoose the protocol revision, import a log, correct the structure, and compare expected with actual JSON.

Quick tools for the small stuff.

Open one focused utility when you already know the exact transformation you need.

All tools

A result is useful when you know what changed.

The URL workflow shows the cleaned list and the decisions that produced it. Nothing is crawled in the background.

Before
https://EXAMPLE.com/
https://example.com
https://example.com/page/#top
https://example.com/page?utm_source=news
https://example.com/about/
After · 3 unique URLs
https://example.com/
https://example.com/page
https://example.com/about

Duplicate root removed. Host normalized. Fragment, tracking parameter, and trailing path slashes removed.

See the crawl-list workflow

Private by default.

No account, no uploads, and no saved input. Anonymous usage events never include tool inputs or generated outputs.

Examples, limits, and evidence.

The useful details live next to the job: realistic inputs, edge cases, technical limits, and reproducible tests.

Practical guidesUse a method when the decision matters more than the transformation.Tested edge casesSee how the main workflows handle messy inputs and ambiguous signals.Published field testsInspect the repository fixtures, runners, results, and review limits.