​
What it does

Runs five independent technical checks against your domain at the same time: a full site crawl, crawl-error analysis, Core Web Vitals scoring, indexability checks, and structured-data validation.

​
Why you should use it

It’s the safest possible first workflow to run — entirely read-only, it changes nothing on your site. Recommended as your very first MAEL run.

​
Where to find it

Trigger it by its ID, technical-audit.

​
What information you must enter

For your first run, the JSON above with just domain_id is enough — every other field has a sensible default.

​
Step-by-step

1

Trigger the workflow with just domain_id

See Run Your First SEO Workflow.
2

Watch the five checks run in parallel

Unlike most workflows, these five steps have no dependency on each other — they all start at once.
3

Review the findings once complete

Open the run and look at its output.

​
What happens after you click Trigger run

A real crawler visits your live site. On shared or budget hosting, a large crawl can be noticeable — max_pages/crawl_depth let you limit its scope, and it always respects your site’s robots.txt.

​
How long-running work is shown

The five checks run genuinely in parallel — watch all five progress at once on the execution timeline. This is usually the fastest of the five workflows to finish.

​
How to understand the output

There’s no single pass/fail score here — each finding is a specific, actionable issue, not a percentage.

​
What action to take based on the output

  • Crawl errors → fix the broken URLs, or confirm they’re intentionally removed
  • Low Core Web Vitals → typically a hosting/theme/image-optimization issue outside MAEL’s scope — pass to whoever manages your site’s technical infrastructure
  • Non-indexed articles you expected to rank → check for an accidental noindex tag or a robots.txt block

​
Common mistakes

  • Running a full check_mode audit very frequently on a large site — new_content_only (the default) is lighter and usually sufficient for routine checks.

​
Troubleshooting

See Troubleshooting.