Documentation · Pages

Site map

Every page on your site by folder, what your report and the daily checks found on each one, and what your agents are doing about it.

The Site map is at https://app.ivyl.ink/sitemap. Open Site map in the nav. The link shows for sites that went through setup at /onboarding, even if you skipped the report there. If you don't see it, open the address above directly.

Use it to work page by page: find the pages with the most to fix, open one, and see its scores, its issues and your agents' work on it in one place.

Where the pages come from

The Site map joins two sources:

Your latest report. When a report is released, every page it read is added, with what its checks and PageSpeed Insights found there. This part is a snapshot from the report's date. A newer report replaces it.
Your sitemap, read by the daily checks. New pages show up here before your next report tests them. The daily checks run once a day while your agents are on and your plan is active. See Turn agents on.

Daily findings and your agents' work are always current. Only the report's part is dated.

A line under the tabs tells you which you are looking at:

Line	What it means
What the report found is from your report on date. Daily checks and agent work are up to date.	The report's findings are from that date. Everything else is live.
These pages come from your sitemap. Your next report tests each one.	No report has tested these pages yet. You see the page list and daily findings only.

The Site map keeps up to 20,000 pages from your sitemap. A page that has no report data and hasn't been in your sitemap for 30 days is removed.

How Ivy Link finds your sitemap

The daily checks look for your sitemap the same way a search engine does:

It reads the Sitemap: lines in your robots.txt.
If there are none, it tries /sitemap.xml on your site.
It then reads every child sitemap that file lists.

Only pages on your own site are kept.

Confirm it during setup

Step 2 of 4 when you build your first report is Confirm your sitemap. Ivy Link looks for it right after you start, so the step is often filled in already. If it found one, you see "Using" with the sitemap's path and its page count, for example "Using /sitemap.xml — 1,240 pages." You have three choices:

Find it for me (or Find it again once one is set): Ivy Link looks it up the same way.
Paste a URL into Sitemap URL and press Use this sitemap. It must be on your own site. If it isn't, you see "Use a sitemap URL on your own site."
Crawl without one: you see "Okay — the crawl will start from your homepage."

If nothing was found, the step says "No sitemap found; the crawl starts from your homepage." See Your first report for the other steps.

The sitemap you confirm here is the one your first report reads. The daily checks don't use it: they always look in robots.txt, then at /sitemap.xml. If your sitemap lives somewhere else, add a Sitemap: line for it to your robots.txt so the Site map can keep up with new pages.

If your sitemap has a problem

The daily checks note when a sitemap returns an error or doesn't load, and when pages left your sitemap that week. Your agents look at what the daily checks find and suggest work for what matters. While any sitemap fails to load, the Site map's page list isn't updated from it, so pages don't look gone by mistake.

With your agents on and Search Console connected with full access, Ivy Link also submits changed sitemaps to Google, about once an hour. See Search Console.

The two views

The page opens with the heading Site map and two tabs: All pages and Pages with something to fix.

All pages

Pages are listed by folder, 200 rows at a time. Press Show more for the next 200. Breadcrumbs above the list start at your site's host and go down through each folder. Click any part to go back up.

Each row is one of two kinds:

A page. Its name (your homepage shows as Home page), its title, and a pill. If folders sit below it, a link says how many, for example "12 pages inside, 3 to fix."
A folder with no page of its own. Its name with a trailing slash, the number of pages inside, and a pill such as "3 to fix" if any of them need work.

The pill on a page row means:

Pill	What it means
N things to fix	Your report's checks, its PageSpeed Insights findings and the open daily findings add up to N on this page.
Nothing to fix	Your report tested this page and found nothing.
Not tested yet	Only your sitemap has this page. Your next report tests it.

Pages with something to fix

This view ranks pages by how much there is to fix, most first. Each row shows the page's path (your homepage shows as Home page). The count adds the report's checks, its PageSpeed Insights findings and the open daily findings. It shows the top 200. If there are more, it says "These are the 200 pages with the most to fix."

If nothing needs work, it says "Nothing to fix on any page." Before any report, it adds "yet. Your next report checks each one."

One page in detail

Click a page to open it. You see breadcrumbs, the page's title, and a link to the live page.

Under the link is a line about where the data comes from:

With report data: the report's date, then facts such as Kept out of search (noindex), Not found or Couldn't be read, the word count, "N links from your other pages" and "N clicks from Google search."
Only in your sitemap: "Your next report tests this page."
In neither: "Ivy Link hasn't seen this page in your sitemap or your report. Your agents' work on it shows below."

The page then has four sections.

PageSpeed

If your report tested the page, you see three score tiles: Accessibility, Best practices and SEO. Below them, What PageSpeed Insights flagged lists its speed, best-practice and SEO findings. A link opens the full PageSpeed Insights report, where you see the speed scores.

If nothing was flagged, it says "PageSpeed Insights flagged nothing about speed, best practices or SEO on this page."

Reports test a sample of your pages with PageSpeed Insights, not all of them. For a page that wasn't tested, you see "Your report didn't test this page with PageSpeed Insights." (or, before any report has read it, "Your next report tests a sample of your pages with PageSpeed Insights.") and a Test it on PageSpeed Insights link so you can test it yourself.

Issues found

This lists the problems on the page. Each one is tagged with where it came from:

Your report: checks from your latest report.
Daily checks, since date: open findings from the daily checks, most serious first. The page shows up to 20.

If there are none, it says "No issues found on this page." For a page your report hasn't read, it says "The daily checks found nothing here. Your next report checks this page in full."

The report's checks read like this:

Check	What it says
Missing title	It has no title, so search results show a worse one.
Duplicate title	It shares its title with another page, so search engines can't tell them apart.
Missing description	It has no meta description, so Google writes its own snippet.
Duplicate description	It shares its meta description with another page.
Missing H1	It has no main heading (H1).
Several H1s	It has more than one main heading (H1).
Thin page	It has very little text (under 150 words).
Noindex	It's marked noindex, so search engines leave it out. Check that's intended.
Canonical elsewhere	Its canonical link points to another page, so search engines index that one instead.
Missing alt text	Some of its images have no alt text.
No product data	It's a product page without Product structured data.
Broken links	It links to pages on your site that error.
Not found	It answers "not found". Redirect it to the closest live page, or bring it back.
Couldn't be read	Your report couldn't read it (a timeout or a server error). Check it by hand.

Design

This collects what affects how the page looks and reads: layout shift and accessibility findings from PageSpeed Insights, visual findings from the daily checks, and any design-review work your agents have on the page. If there is none, it says "No design issues found on this page."

Agent suggestions and results

Your agents' ideas and work for this page, in three groups:

Group	What's in it
Ideas waiting for your OK	Ideas that need your approval. Each has a Waiting for your OK pill.
Being worked on	Approved work (pill: Approved), work in progress (pill: In progress), and ideas your standing approval lets agents start (pill: Your agents start this).
Finished	Work that has shipped or been measured (pill: Shipped or Measured).

If there is nothing yet, it says "Your agents haven't suggested anything for this page yet." A linked pull request shows its number and whether it is Open, Merged or Closed.

Find what to fix, page by page

Open Site map in the nav.
Choose Pages with something to fix to see the worst pages first. Or browse folders under All pages.
Open a page. Read PageSpeed, Issues found and Design.
Under Agent suggestions and results, press Approve or Drop on each waiting idea. You come back to the same page.
For work already under way or finished, press See it on Results to follow it on Results.

After a report is released and before you pick your first priorities, its actions show Pick it on your report instead of Approve and Drop. Pick them on the Report page first. After that, you can approve or drop them here.

See Approve work for how approvals work across the app.

Before there are pages

Until the Site map has pages, it shows one line instead of the list:

What you see	What it means	What to do
Add a site first.	Your account has no site.	Add one at app.ivyl.ink/sites/new (account owner only). See Sites.
Your site map fills in when your report is ready: every page it reads, and what it found on each one. Follow your report	Your first report is building.	Follow it on the Report page. The Site map fills in when it's released.
Your pages show here after the daily checks read your sitemap, or after your first report.	No report yet, and the daily checks haven't listed any pages.	Build a report from /onboarding. Or, with your agents on, wait for the next daily check.
Ivy Link hasn't found your site's pages yet. They show here after the next daily check reads your sitemap.	Your report is released but no pages are listed.	Wait for the next daily check. Make sure your sitemap is listed in robots.txt or at `/sitemap.xml`.

If pages still don't appear, see Troubleshooting or email hello@ivyl.ink.

Last updated October 31, 2026

Something here not match what you see? Email hello@ivyl.ink and we'll fix the page.