How to use the QA Automation Engineer

A step-by-step guide for customers who already have the QA Automation Engineer in one of their seats.

By Al, BuzFind founderUpdated Portland, Indiana (Reading, PA roots)
QA Automation Engineer AI agent - Broken Page Checks
The QA Automation Engineer - Broken Page Checks

This guide shows you how to run the QA Automation Engineer, what to type, and how to read what it sends back. To see what it checks and which plans include it, read the QA Automation Engineer page.

Before you start

  • Your site address, plus a note of the pages you changed lately. New edits are a common place for broken links to start.
  • A list of pages you removed or renamed, so you can match them to the 404 errors in the report.
  • The QA Automation Engineer picked in one of your seats under My AI agents, with Save selection clicked. If it is not, its findings show as Locked.

Step by step

  1. Sign in and open My AI agents in the dashboard menu. Click the QA Automation Engineer to put it in one of your seats, then click Save selection.
  2. Open the Dashboard page. In the chat box, type what you need in plain words and include your website address.
  3. Wait while the check runs. The answer shows in the chat, and the full report is saved under Audit reports & fixes.
  4. Make the changes you agree with, then send the same request again to see what is still open.

What to type in the chat

Copy one of these requests and change the details to match your business.

“Find broken links on yourbusiness.com”
The main request. It starts the QA Quality Audit, which reads up to 15 pages.

“Check yourbusiness.com for 404 errors”
Use this after you remove, rename or move pages.

“Find broken links on yourbusiness.com/blog/”
Use this when one section, like your blog, has many links. The check starts from the page you type.

How to read the results

  • Error items name the page or link and the status it returned, such as 404 (not found) or 500 (server error).
  • Broken link items name the link that failed. The check tests up to about 40 links between your own pages.
  • Console error and accessibility items come from the one PageSpeed test, so they only cover the page you typed.
  • The QA Quality Audit also runs the Code Reviewer, so heading and alt text items may show too, or as Locked if that agent is not in your seats.

What to do next

  • Fix 500 errors first. Those are server problems your host or web person needs to look at.
  • Fix 404 links by pointing them to the right page, or add a redirect if the page moved.
  • Run the check again after your fixes to confirm the errors are gone.

Tips

  • Links to other websites are not tested, only links between your own pages.
  • On a bigger site, start the check from different section pages to cover more of it.
  • Layout and design questions belong to the UI/UX Enhancer.

Questions about using it

Why does a link that works for me show as broken?

The check visits your site from our server. If a firewall or security plugin blocks unknown visitors, a page can fail for the check but work for you. Ask your host about it.

Can I check more than 15 pages?

Not in one check. Start a new check from a different page, like a section page, to reach other parts of your site.

What does it mean if no issues are found?

You see No issues found. The pages and links it tested all worked at that moment.

Agents work better together. Here are specialists that pair well with the QA Automation Engineer:

  • UI/UX Enhancer - Checks your pages for things that make it harder for visitors to take the next step, and suggests specific changes.
  • Speed Optimizer - Finds what makes your site slow, especially on phones, and gives you a fix list with the biggest wins first.
  • Code Reviewer - Checks the HTML on your pages for structure problems: heading order, missing page landmarks like main and nav, and images with no alt text.

Need a different agent? Browse all 25 agent guides or see the full agent catalog.

Was this article helpful?