How to use the Code Archaeologist

A step-by-step guide for customers who already have the Code Archaeologist in one of their seats.

By Al, BuzFind founderUpdated Portland, Indiana (Reading, PA roots)
Code Archaeologist AI agent - Heavy and Old Code Checks
The Code Archaeologist - Heavy and Old Code Checks

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

Before you start

  • Your live website address. The agent reads the page code your site sends, so you do not need to share logins or files.
  • A short list of the plugins, chat widgets and tracking tags you know you added, so you can match them to the scripts the report names.
  • The Code Archaeologist 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 Code Archaeologist 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.

“Check yourbusiness.com for old code and outdated scripts”
Use this when you took over a site and want to know what loads on it.

“Find legacy jQuery on yourbusiness.com”
Use this when you think an old library still loads on your pages.

“Check the old code on yourbusiness.com/contact/”
Use this when one page feels heavy, since the check and the PageSpeed test start from the page you type.

“Run a code health audit on yourbusiness.com”
Use this when you want to name the Code Health Audit directly.

How to read the results

  • Each item names a script, file or markup pattern and the page where it shows up. Scripts from other companies are named by their web address.
  • Items about files that block the page and unused CSS or JavaScript come from the one Google PageSpeed test, so they apply to the page you typed.
  • Speed tips only show when the saving is real (150 ms or 30 KB or more). If the page already passes every Core Web Vital, you will not see those tips at all.
  • The Code Health 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

  • For each outside script, ask yourself if you still use that service. If not, removing the tag is often the simplest fix.
  • For changes like loading a script later, click Copy fix instructions and send the text to whoever edits your site.
  • Run the same request again after the changes go live to see which items are gone.

Tips

  • Run it again after you add a plugin, a chat widget or a tracking tag. New add-ons are a common way new scripts end up on every page.
  • Overall speed scores belong to the Speed Optimizer. The Code Archaeologist names the code behind a problem.
  • It cannot see pages behind a login, so a members area or an admin screen is not checked.

Questions about using it

Can I check a page that is not my homepage?

Yes. Type that page's full address. The check starts there and the PageSpeed test runs on that page.

Why does a script I removed still show up?

The check reads your live site at the moment it runs. If a cache still sends the old page, clear the cache and run the check again.

What does it mean if no issues are found?

You see No issues found. None of the pages it read had heavy outside scripts, blocking files or old markup it could point to.

Agents work better together. Here are specialists that pair well with the Code Archaeologist:

  • 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.
  • Technical SSR Sentinel - Checks your pages for technical SEO problems that stop search engines from finding, crawling, or indexing them.
  • Security Sentinel - Checks the security settings anyone can see on your site, like HTTPS and security headers, and returns a report with fixes ranked by severity.

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

Was this article helpful?