Buy

SEO & Accessibility

SEO package

The SEO & Accessibility page (SEO in the sidebar) belongs to the SEO package. An audit crawls a website from your Mac and rates it like a site audit: a score from 0 to 100, findings by severity, a table of every page, resources, a history across runs and reports as PDF, CSV and JSON. If you want, the same audit also checks accessibility against WCAG 2.2 in a Chrome browser on your Mac. On top of that come the website check, which looks at the site as a whole, and the page inspector for single addresses.

Everything runs locally, with no API keys and no third-party service. An audit never starts automatically, only when you trigger it. You check local WebDonkey sites exactly like public websites.

What you do here

Page layout

At the top is a bar with the projects as a filter (All and one entry per project with its number of audits). To the right: Search audits…, Check a URL now, New project and New audit. The projects are the same as in the Monitor. A new project appears in both views.

Below, each project has a section:

  • The header with the project name and three buttons: New audit, Rename project and Delete project. Deleting removes the whole project, in the Monitor too, with all reports, histories and uptime targets.
  • Figures across all audits of the project: Lowest score and Average score (from two audits on, with one audit Score), Errors, Warnings, Pages checked, and Running while audits are running.
  • One card per audit, sorted by name.

An audit card

  • On the left, the score in its tile (without an SEO check, the accessibility score), the label, the host and the state: Last run …, No run yet, Crawling… or Interrupted.
  • In the middle, the kind (Full audit, Section with its directory, Single pages), for full audits across all subdomains All subdomains of the domain, the budget (max. 10,000 URLs) or the number of listed pages. Below are the Accessibility score, errors, warnings, notices, pages and the trend against earlier runs as a small curve with the difference. If the run ended incomplete, the reason is shown in yellow.
  • On the right: Run audit (or Stop while it runs), Save report as PDF, Edit, Delete and Open audit.

While an audit runs, the card shows the progress at the bottom. Clicking the card opens the report.

Free and Premium

The SEO package is a package of its own, not part of Premium. You assign it to a licence in your account (see SEO package). Without the package, the SEO entry in the sidebar carries a lock, and the page explains what the package unlocks. View in shop takes you to the shop. Your existing audits stay visible and can be deleted. New audits, starting, the website check, checking a URL now and exports are locked (Needs the SEO package). If you bought the package but have not assigned it to a licence yet, the page says so and Assign in account takes you there.

With the SEO package but without Premium, the Monitor's limit applies: one project with three entries, uptime targets and audits counted together. Premium removes it. Prices are on webdonkey.io/pricing.

Create an audit SEO package

An audit entry defines what gets checked: which address, how far the crawler may go, whether SEO, accessibility or both are checked, and with which login. Creating it starts nothing yet. The audit only runs when you start it, and you can repeat it as often as you like afterwards.

Where to find it

  • On the SEO page at the top right: New audit. The audit goes into the filtered project, otherwise into the first project that takes entries.
  • In a project header: the plus (New audit).
  • In the search (⌘K): New SEO audit.

If there is no project yet, create one first (New project). It shows up in the Monitor as well.

How to do it

  1. Click New audit. The dialog is called New audit and reminds you: An audit only runs when you start it.
  2. Pick the kind:
    • Full audit: crawls the whole website from the start address, up to the URL budget.
    • Section: crawls one directory and everything below it, for example /blog/.
    • Single pages: checks exactly the pages you list, no crawl. More in Check a URL list.
  3. Enter a Label if you like (default: the hostname) and pick the Project.
  4. Under What to check, choose SEO, Accessibility or both. New audits check both, and one always stays on. With Accessibility on, the Accessibility section with its settings appears below.
  5. Enter the Start address, for Section the Address of the section, such as example.com/blog/. Without https://, WebDonkey assumes HTTPS.
  6. For Full audit only: pick the Crawl scope.
  7. Pick the URL budget. Below it you see the longest the audit can take with these settings.
  8. Optional: Filter pages to leave out areas before the first run (see below).
  9. Optional: SEO keywords (comma-separated, optional).
  10. If the site is protected, tick Site is password-protected (.htaccess / Basic Auth) and enter User and Password.
  11. Optional: expand Advanced crawl settings. Collapsed, the line shows a summary such as "Depth 20 · 200 ms pause · exclusions: 0".
  12. Click Save.

The audit appears as a card in the project. Start it as described in Start an audit.

Fields and options

Field Meaning Default
Label Name of the card and the report. Hostname
Project Which customer the audit belongs to. When editing, you move it to another project here. selected project
What to check SEO, Accessibility or both. Both need only one crawl: every page is fetched once, then checked in Chrome. both
Start address Where the crawler starts and follows links. empty
Address of the section The directory the crawler stays in. Below the field it says what is checked, for example "Only example.com/blog/ and everything below it is checked." empty
Crawl scope This subdomain only: exactly this host, with and without www treated the same. All subdomains of the domain: also shop., blog. and other subdomains. Other domains are never fetched. This subdomain only
URL budget Maximum number of URLs crawled: Sample (100), Small (500), Medium (2,000), Large (10,000), Very large (50,000). Another value from the settings shows as Custom. 10,000, 500 for a section
Filter pages Paths the audit leaves out. nothing excluded
SEO keywords (comma-separated, optional) The audit checks whether each keyword appears in title, description, H1 and text. empty
Site is password-protected (.htaccess / Basic Auth) Login for every request of this audit, only sent to this website's own address. off
Advanced crawl settings Max. URLs crawled, Max. click depth, Do not crawl, and under Advanced pause, parallel requests, robots.txt, parameters, user agent, external links and resources. Details in Audit settings. see there
Additional pages (one per line, optional) In the advanced settings: pages nothing links to, such as campaign landing pages. The crawler would not find them otherwise. empty

Save only works once a project is picked and an address is entered. For Section the address has to include a directory, otherwise it says Add the directory to the address, for example example.com/blog/. Without one this would be the whole website. With password protection, a user is required.

Filter pages

With Filter pages you decide before the first audit which areas it leaves out, for example /media/, /bundles/ or a language tree.

  1. Click Scan site. WebDonkey reads robots.txt and the sitemaps and follows the links from the start address, with the audit's settings and at most up to the URL budget. The progress shows how many pages were fetched and how many URLs were found. Stop ends the scan.
  2. The URLs found appear as a path tree, already while the scan runs. One click on a path takes it out of the audit, a second click puts it back. At the top you see how many URLs are excluded.
  3. Done applies the selection. Scan again reads the site once more.

The path to the start address is marked Start and always stays in, because the audit always crawls the start address. Every excluded path then appears as a pattern under Do not crawl. Patterns you type there by hand show up as excluded in the tree too. For very large sites the tree only lists part of the URLs and says so. The Filter pages row is also available later in the Settings tab.

What happens in the background

  • The dialog remembers unsaved input, even across a restart. The next time it opens, it says Unsaved input from last time has been restored. with Reset. The password is never part of the draft.
  • If you close the dialog with input in it, WebDonkey asks Discard your input?.
  • The password is stored encrypted in WebDonkey's database.
  • The Filter pages scan fetches the website like a short audit, only the selection is saved.

Changing it later

Edit on the card opens the Edit audit dialog with the same fields. You also change crawl settings, keywords and pages in the report's Settings tab.

Free and Premium

Audits need the SEO package. Without Premium, the Monitor's limit applies: one project with three entries, uptime targets and audits together. At the limit, New audit is locked and the tooltip names the reason. An audit locked after switching to Free can only be renamed.

Troubleshooting

What you see Why What to do
New audit is grey, tooltip Needs the SEO package The SEO package is not active. Assign the package to the licence in your account, see SEO package.
New audit is grey, the tooltip names the Free limit The project already has three entries. Delete an entry or activate Premium.
Warning under Address of the section The address names no directory. Add the directory, for example /blog/.
The scan stops after a few URLs The server throttles or blocks the crawler. Raise the pause in the advanced settings or switch the user agent.

See also

Check a URL list SEO package

The Single pages kind checks exactly the pages you list: no crawl, no sitemap, no following of links. Twenty pages are done in seconds. That suits the pages that matter most, such as checkout, contact or campaign landing pages, and a quick check after a deployment.

Where to find it

SEO page › New audit › Single pages. On the card and in the report, this kind is called URL list.

How to do it

  1. Click New audit and pick Single pages.
  2. Enter the website under Website, for example example.com.
  3. In the Pages to check table, enter one Path per row, such as /checkout or /en/contact. Add row adds a row, the trash can removes one.
  4. Under What to check, choose whether the pages are checked for SEO, accessibility or both.
  5. Optional: keywords and password protection as for any audit.
  6. Click Save and start the audit.

Many addresses at once

If you copy several lines, say a column from a spreadsheet, and paste them into one row of the table, WebDonkey spreads them over separate rows. Full addresses on this website are shortened to their path. An address on another host stays whole and is checked as written. Below the table you see the number of pages.

What differs from a crawl

  • There is no URL budget, no crawl scope, no click depth and no Filter pages.
  • The report has the same structure. Findings that only make sense for a crawl are left out: orphan pages and excessive click depth.
  • There is no Not crawled tab.
  • You change the list later in the Settings tab under Keywords and pages: one page per line. A path such as /checkout belongs to the audit's website, a full address is checked as written. You change the accessibility settings with Edit on the card.

Free and Premium

Like every audit, a URL list needs the SEO package and counts as one of the project's three entries on Free.

Troubleshooting

What you see Why What to do
A row is checked on another host You pasted a full address of another host. Shorten the row to its path, or create a separate audit for the other host.
The start confirmation lists fewer pages than expected Empty rows do not count. Check the table.

See also

Start, stop, resume an audit SEO package

An audit only starts by hand, never on a schedule and never through Check all in the Monitor. Before it starts, you confirm what will happen: scope, pace, the longest it can take and what this run checks. After that the audit runs in the background, even if you close WebDonkey.

Where to find it

  • On the audit card: the play icon (Run audit).
  • In the report at the top right: Run audit.
  • On the command line: wd seo crawl, see Monitor and SEO.

How to do it

  1. Click Run audit. The confirmation Start the audit of “…”? opens.
  2. Under What this run checks, pick SEO and accessibility, SEO only or Accessibility only. Preselected is what the audit has under What to check.
  3. Read the summary: crawl scope, Max. URLs crawled, Max. click depth, pause, Parallel requests, robots.txt, the exclusions and the longest duration. For a URL list it says how many pages will be checked.
  4. With accessibility it also lists the level, the screen widths and how many pages get the deep check, such as "Accessibility: WCAG 2.2 AA, widths 1280, 390 px, deep check on up to 10 pages."
  5. Click Start audit.

Re-check only accessibility

If you pick Accessibility only and there has been a run before, you can tick Only check the … pages of the last run (no crawl). Chrome then loads exactly these pages without a new crawl. That saves time when you only want to check accessibility after some fixes.

Stop

Click Stop (the square on the card) and confirm with Stop audit. Keep running closes the confirmation. Stopped means graded, not thrown away: the URLs crawled so far are graded, and the report is marked Stopped and incomplete.

Interrupted

If the background process was ended, for example by restarting the Mac, the audit shows Interrupted and Interrupted after x URLs. On the card or in the report you then pick:

  • Continue: carry on where it stopped.
  • Grade what is there: grade what has been crawled so far.
  • Discard: delete the crawled URLs without grading. The previous report stays.

If the intermediate data is gone, the message says so, and only Discard remains.

While the audit runs

A progress bar shows the phase: Starting in the background…, Reading robots.txt…, Reading the sitemaps…, then while crawling something like "120 of max. 10,000 URLs · 340 found", followed by Checking external links…, Checking resources… and Grading…. With accessibility, Starting Chrome for the accessibility check… and "Checking accessibility… 12 of 40 pages" are added. In the report you also see the elapsed time and the address being fetched.

The previous report stays visible until the new one is done. A note then says A new audit is running. Below is still the previous report. When the audit finishes, it reports in the bell.

What happens in the background

  • The audit is a process of its own. You can leave the page or close WebDonkey, it keeps running and keeps the Mac awake. If you close a MacBook's lid it sleeps anyway, and the audit carries on afterwards.
  • If the internet connection drops, the audit waits (No internet connection) and then continues, instead of reporting pages as broken.
  • The crawler honours a Crawl-delay from robots.txt. If the server answers with "too many requests", it slows down and stops after repeated refusals. The report then ends with Throttled by the server.
  • If the website stops answering during the run, the audit ends with Site stopped answering.
  • The crawler identifies itself as WebDonkey-Monitor/1.0, unless you set a browser user agent in the settings.
  • External links are only fetched with Check whether external links work on, and then with a single request per address.

Free and Premium

Starting needs the SEO package. An audit locked after switching to Free cannot be started, its report stays readable.

Troubleshooting

What you see Why What to do
Start audit in the confirmation is grey, with a note about Chrome, Node.js or the check module below Something is missing for the accessibility check. Follow the note, for example Install check module. SEO only can be started anyway. See Check accessibility.
The audit failed The run could not produce a report. The reason is shown below. Fix the reason and pick Run audit again. The previous report stays.
Ends with Throttled by the server The server or a firewall refuses too many requests. Raise the pause, lower Parallel requests or allow the WebDonkey-Monitor/1.0 user agent in the bot protection.
Ends with URL limit reached The budget ran out. Raise the budget or exclude areas, see Not crawled.
Yellow note "Accessibility not checked: …" The SEO check ran, the accessibility check did not. Fix the reason and start Accessibility only.

See also

Report: Overview SEO package

The Overview tab sums up the last audit on one page: the score, the counters, what changed since the last run, the most frequent issues and charts for the whole website. From here, one click takes you to the findings or to single pages.

Where to find it

SEO page › click an audit card. The report opens on the Overview tab. All audits at the top left takes you back to the list.

The report header

Above the tabs are the label, the address, the kind (Crawl or URL list) and the project. Below are the state (Last audit: …), the duration, how the audit ended (such as Completed or URL limit reached) and the score. On the right are Run audit and the buttons under Export (see Export reports).

The tabs show their count, such as the number of findings next to Issues. The Accessibility tab is there as soon as the audit checks it, Not crawled does not exist for a URL list.

What you see

  • Score: the overall value (Total) from 0 to 100 and one value each for Content, SEO and Technical. Below, "x URLs crawled · y found" and the duration.
  • Counters: Pages checked (out of how many found), Errors, Warnings and Notices with the number of finding types, Indexable (with the number of non-indexable pages), Avg. response (with the slowest page), Avg. words (with the total word count) and Missing alt text (with the total number of images).
  • Since the last audit: score, errors, warnings and pages compared with the audit before, plus the findings that are New, Fixed or Changed. On the first audit there is nothing to compare yet. If one of the two audits was incomplete, the comparison is only a rough guide.
  • Score over time: the scores of the last audits as a curve, from the second audit on.
  • Most frequent issues: the most important findings. All x findings switches to the Issues tab.
  • Findings by severity (Error, Warning, Notice): occurrences across all pages. One click jumps to the Issues tab, filtered on that severity.
  • Charts: Status codes, Indexability, Click depth (clicks from the home page, important pages belong in the first three), Response time, Words per page, Title length (30 to 60 characters show in full in search results), Description length (70 to 160 characters) and Page size (HTML only).
  • Slowest pages, Largest pages, Pages with the most findings and Most linked pages: one click opens the page in the Pages tab.
  • Keywords: where each stored keyword appears, in Title, Description, H1 and Text.
  • Content and markup: Most frequent terms, the Structured data types found and the external link targets, either just counted or, with the check on, with the number that are unreachable.

How the score is calculated

Every error and every warning costs points, weighted by the share of pages it affects. Ten broken links weigh more on a 20-page website than in a shop with 10,000 pages. Notices never cost points: login, cart and checkout, for example, belong on noindex, and that is not an error. The total is never better than the weakest area. Ignored findings do not count (see Issues).

The score is a sorting aid, not a Google metric. If the report shows an incomplete end, such as URL limit reached or a stop, every figure only describes the pages that were checked.

Troubleshooting

What you see Why What to do
No audit yet The audit exists but has not run. Run audit.
The first audit is running Scores and charts appear once the crawl is graded. Wait. You can leave the page.
A chart reports missing data The audit comes from an older version. Run the audit again.
The stored report cannot be read. Run the audit again to create a new one. The stored data is damaged. Run the audit again.

See also

Report: Issues SEO package

The Issues tab lists every finding of the last audit, grouped into the areas Content, SEO and Technical. Each finding explains what it means and what you can do, and names example addresses. From here you jump to the affected pages or take a finding out of the score.

Where to find it

Report of an audit › Issues tab. From the Overview you also get here via All x findings or by clicking a severity.

How to do it

  1. Pick the severity at the top: All, Errors, Warnings or Notices. Each button shows how many finding types there are.
  2. Read a finding: title, count, severity, on how many pages it occurs (or Whole website), the explanation and a few example addresses. Show x more examples reveals the rest, Show fewer examples hides them again.
  3. Click Show affected pages. The Pages tab opens, filtered on this finding. For broken links you see under Inlinks which pages carry the link.
  4. If a finding is intended for this website, click the crossed-out eye (Ignore (no longer counts towards the score)).

Layout of the list

Section Content
Content, SEO, Technical The findings per area, with the area's score in the header.
Ignored Findings you excluded. Show expands them, Hide collapses them. The eye (Count again) puts a finding back into the score.
Crawl Facts about the run itself, such as a URL limit reached or skipped areas. They never count towards the score.

If there are no findings, it says No issues found.

What is checked

A selection of the checks, by area:

  • Content: page title and meta description (missing, too long, very short, duplicate, not matching the content), H1 (missing, multiple, the same on several pages), skipped heading levels, thin content (under 200 words in the main content), duplicate content, placeholder text, images without alt text, links without link text, hard-to-read text, Open Graph and Twitter card.
  • SEO: home page unreachable, robots.txt blocking the website, pages with 4xx and pages linking to them, redirects (temporary, chains, loops, without target, to other domains, via meta refresh), canonical (missing, pointing to a redirect or an unreachable page), noindex and nofollow, hreflang, broken structured data, sitemap and robots.txt (missing, broken or redirected URLs, noindex pages in it), orphan pages, pages more than four clicks deep, internal links to http:// and broken external links.
  • Technical: server errors (5xx) and pages with no answer, mixed content, broken resources, slow pages (over 2 s) and slow server responses, very large HTML (over 500 KB) and large images, missing compression and cache lifetime, viewport, language attribute, doctype, character set, HSTS, favicon, images without dimensions, very long URLs, many blocking files in the head and outdated HTML elements.

What happens in the background

Ignoring applies to this audit and every later run. The finding stays visible in the report but no longer counts towards the score. The score is recalculated right away.

Troubleshooting

What you see Why What to do
No findings of this severity. The chosen filter matches no finding. Pick All.
Show affected pages is missing The finding concerns the whole website, not single pages. Read the explanation in the finding.
A finding comes back after the next run It was counted again or appeared anew. Look under Ignored.

See also

Report: Pages SEO package

The Pages tab is the table of every URL the audit fetched. On the left is the list, on the right every value of the selected page: status, response time, title, description, headings, links, findings and who links to the page. That way you find the pages carrying a broken link right away.

Where to find it

Report of an audit › Pages tab. From the Overview and Issues tabs, clicking a page or Show affected pages takes you straight here, already filtered.

How to do it

  1. Search with Search pages (URL, title, description)… or filter:
    • by finding (All findings or a specific finding with its count)
    • by status (All statuses, 2xx, 3xx, 4xx, 5xx or Unreachable)
    • Only with findings hides pages without findings.
  2. Pick an Order: In crawl order, Most findings first, By status code, By address or By host. By host groups the list under one heading per host, and the host of the start address is marked start domain. That helps with audits across several subdomains.
  3. Below the filters you see how many pages match ("x of y pages"). The list shows 100 pages at a time, Previous and Next page through it.
  4. Click a row. The page's values appear on the right.

List columns

Column Meaning
Status HTTP status, coloured by the most severe finding. n/a if no answer came.
Page Path of the page (with host for other hosts) and its title below, or the target for a redirect.
Time Response time.
Warning triangle Number of findings on this page.

The values of a page

  • Status, Final URL after redirects and the number of redirects, Response time, First byte (TTFB), HTTP version, Size and Transfer (compressed or not).
  • Indexable: yes, No (noindex), No (canonical points elsewhere) or not because of the status. Also whether the page is in the sitemap.
  • Title, Description (with character count), H1, Canonical, Language and the number of language versions (hreflang).
  • Words (with the share in the main content and the text share of the HTML), Readability, Images (and how many lack alt text), Links (internal, external, nofollow).
  • Headings with the Outline, Click depth (clicks from the home page) and Link strength, an internal PageRank: how strongly the page is linked within the website.
  • Scripts and styles with the number of render-blocking files, and Broken resources.
  • Outgoing problems: links on this page to broken URLs and to redirects.
  • Inlinks: every crawled page that links here. If none does, it says No crawled page links here.
  • The page's findings.

Inspect (Fetch this page again now and analyse it in detail) opens the page in the page inspector, with this audit's settings, keywords and login. Back to the page table returns.

What happens in the background

The table belongs to the last run and is replaced by the next run. The data is on your Mac, nothing is fetched while you page through it. Only Inspect requests the page again.

Troubleshooting

What you see Why What to do
No page table The page list no longer exists, for example after restoring a backup. Run the audit again.
No page matches the search. Filter or search is too narrow. Reset the filters.
A page is missing entirely The audit did not crawl it. Look up the reason in the Not crawled tab.

See also

Report: Website check SEO package

The Website check looks at the website as a whole rather than single pages: security headers, redirects, robots.txt and sitemap, server speed, access for AI crawlers and the domain's mail records. It needs a handful of requests to the website and a few DNS lookups and is done in a few seconds. It runs independently of the crawl and can be repeated at any time.

Where to find it

Report of an audit › Website check tab. On the command line: wd seo check, see Monitor and SEO.

How to do it

  1. Open the Website check tab. The first time it says Not checked yet.
  2. Click Check now. While it runs, it says Checking….
  3. Read the result. At the top are Checked …, the number of checks per state, IP address, Server and HTTP version. Open in browser opens the website.
  4. On a check, click Show explanation and details. You see what the check means, what was found and what you can change. Hide explanation and details collapses it.
  5. After a change to the website, click Check again.

The states

State Meaning
Passed All good.
Needs attention Works, but could be better.
Failed A problem you should fix.
Info A fact without a verdict, such as the HTTP version or an optional file that is missing.
Could not be checked The check could not be carried out, for example because of a DNS timeout. It says nothing about the website.

The checks

  • Security: HTTPS, HSTS (Strict-Transport-Security), Content Security Policy, X-Content-Type-Options, Clickjacking protection, Referrer-Policy, Permissions-Policy, Version numbers in headers and security.txt.
  • Redirects: HTTP redirects to HTTPS, With and without www, Redirect chain of the start address and Error page for unknown addresses (does an address that does not exist answer with 404?).
  • Crawling: robots.txt, Start page open to search engines, XML sitemap, Sitemap named in robots.txt and Favicon.
  • Performance: HTTP version, Compression, Time to first byte, Browser cache for static files and IPv6.
  • AI crawlers: llms.txt, llms-full.txt (both optional) and Access for AI crawlers. The table lists per crawler its Operator, the Access (Allowed, Blocked) and the Deciding rule in robots.txt. Blocking or allowing is fine either way, as long as it is a deliberate decision.
  • Mail: the domain's Mail servers (MX), SPF and DMARC. A local site has no public DNS, so these three are not checked there.

Under Technologies you find the building blocks detected on the website, such as CMS, shop system, web server, CDN, analytics, tag manager, consent banner, fonts and payment.

What happens in the background

The check fetches the home page, robots.txt, the sitemap, a few fixed files such as security.txt and llms.txt, and an address that does not exist. For the mail records it queries the domain's DNS. The result is stored with the audit and goes into the PDF report. The audit's password protection applies here too.

Free and Premium

The website check is part of the SEO package. Without the package, a stored result stays visible and Check now is locked.

Troubleshooting

What you see Why What to do
The website check could not be completed. The website did not answer. Check that it is reachable, then Check again.
Many checks on Could not be checked DNS or the connection failed. Check again later.
MX, SPF and DMARC missing for a local site Local sites have no public DNS. Nothing. That is intended.

See also

Report: Resources SEO package

The Resources tab lists the images, scripts, stylesheets and fonts of the checked pages, each file requested once. You see what is broken, what is too heavy, what is served without compression or without a cache lifetime, and which images are still in old formats. For every file you learn which pages include it.

Where to find it

Report of an audit › Resources tab. You turn the check on and off in the Settings tab under Advanced with Check resources (images, scripts, stylesheets, fonts). It is on by default.

How to do it

  1. Read the figures at the top: All resources, Broken, Too heavy and how many files were checked ("x of y checked").
  2. Filter by Kind (All kinds, Fonts, Images, Scripts, Stylesheets) and by Problem:
    • All resources or With a problem
    • Broken: the file answers with an error or not at all
    • Too heavy: the file is too large for its kind
    • Old image format: JPEG, PNG or GIF instead of a more modern format
    • No cache lifetime
    • Uncompressed
    • Not checked
  3. Sort under Order: Problems first, Heaviest first, Most used first or By address. Search by address… finds a specific file.
  4. On a file, click Show pages to see the pages that include it.

The values of a file

Value Meaning
Size Size of the file.
Type The file type the server reports, such as image/webp.
Compression How the file is compressed when served, such as br or gzip, otherwise none.
Caching The cache lifetime from Cache-Control, otherwise off. Hover over it to see the full header.
"Used on x pages" On how many pages the file is included.

Files on another host carry the note external.

What happens in the background

After the crawl, the audit requests every file it found once, up to four at a time. A crawl deliberately set to a slow pace keeps its pace. At most 5,000 files are checked, the most used first. Not requested are:

  • files blocked by robots.txt. Search engines cannot load them either.
  • files on other hosts, unless the audit also checks external links.
  • files beyond the cap of 5,000.

A note above the list says how many files were left out for which reason. If the audit was stopped or throttled by the server, that is shown there too.

Free and Premium

The resource check is part of the SEO package.

Troubleshooting

What you see Why What to do
The resource check is switched off Check resources is off in the settings. Turn it on and run the audit again.
This audit has no resource data The audit ran before the check was switched on. Run the audit again.
No resources found The checked pages include no such files. Nothing.
Many files Not checked Other hosts or the cap. Read the note above the list, and turn on Check whether external links work if needed.

See also

Check accessibility SEO package

An audit can also check the accessibility of a website. Every page is opened in a Chrome browser on your Mac, checked against WCAG 2.2 and captured as a screenshot. You see the problem spots marked on the screenshot, the WCAG criteria as a matrix, and how the page looks to people with visual impairments or without a mouse. SEO and accessibility together need only one crawl, and every page is fetched once.

Every report and every PDF states what the check means: Result of an automatic check. It does not replace a full audit under BITV 2.0 / EN 301 549.

Where to find it

  • Turn it on: in the New audit or Edit audit dialog, the Accessibility button under What to check. New audits check both.
  • Start it: Run audit, then pick SEO and accessibility or Accessibility only in the confirmation.
  • Read it: the Accessibility tab in the report. It is there as soon as the audit checks accessibility. Its count is the number of elements that are critical or serious.
  • A single address without an audit: Check a URL now, Accessibility tab.

How to do it

  1. Create an audit or open Edit on its card. Make sure Accessibility is active under What to check.
  2. In the Accessibility section, set the Level, usually WCAG 2.2 AA (recommended).
  3. Save and click Run audit. If Chrome, Node.js or the check module is missing, the confirmation tells you what to do (see below).
  4. After the run, open the Accessibility tab. Start with Overview, then Findings and Page.

What is checked

On every page, at every configured screen width:

  • the automatic rules for WCAG 2.2 up to the chosen level, plus best practices if you want
  • WebDonkey's own checks: text on an image or gradient with too little contrast, alt texts that say little, link texts that do not say where they lead ("here", "more"), media with sound that start on their own, and linked documents (PDF, Office) that you have to check separately

On the pages with the deep check also:

  • Keyboard: tab order, visible and covered focus, keyboard traps and elements that look clickable but cannot be reached with the keyboard
  • Layout: reflow at 320 px, text at 200 %, larger text spacing, animations that do not stop
  • Simulations: how the page looks with colour vision deficiencies, blurred vision, low contrast and forced colours (see Comparison images)

What the check cannot decide on its own is listed under To review: a person has to look. Criteria that cannot be tested automatically at all are listed by the report as Check by hand.

Fields and options

The accessibility settings sit in the Accessibility section of the audit dialog and in the Settings tab. Collapsed, the section shows a summary such as "WCAG 2.2 AA · 1280, 390 px · deep check on up to 10 pages".

Setting Meaning Default
Level WCAG 2.2 A, WCAG 2.2 AA (recommended) or WCAG 2.2 AAA. Every criterion up to this level is checked. BITV 2.0 and EN 301 549 require AA. AA
Screen widths (px) The first one is the main width. 320 to 3840 px, at most four widths. 1280, 390
Also check best practices Recommendations beyond WCAG. They are listed separately and never count towards the score. on
Screenshots Of every page, Only of pages with findings or None (close-ups of findings only). Only of pages with findings
Pages with the deep check The home page, then one page per template. With 0, no page gets the deep check. At most 100. 10
Keyboard, Layout, Simulations Which groups the deep check includes. all on
Browser tabs at once More tabs finish sooner but put more load on your Mac and the website. At most 4. 2
Time limit per page (s) For all widths and checks of one page together, 10 to 300 seconds. 45

Pages count as one template when they share the first path segment and the path depth, for example /blog/post-1 and /blog/post-2. Deep-checked pages carry the note deep check in the report.

The score

Every page gets a score from 0 to 100, as in Lighthouse. Each applicable rule weighs by its severity (Critical 10, Serious 7, Moderate 3, Minor 1), and the score is the share of that weight the page passes. A page with any counted violation never shows 100. To review and best practices do not count. The website's score is the average of its pages. The audit card shows it as Accessibility next to the SEO counters.

The Accessibility tab

The tab has five views:

  • Overview: the score with the level (such as WCAG 2.2, level AA), Pages checked (with the number of pages that could not be checked), the elements per severity and what is To review. Below are Elements by severity, Since the previous run (score compared, new and fixed elements), the WCAG success criteria matrix and Weakest pages with the way to All pages.
  • Findings: one card per rule, first the violations by severity, then To review, then Best practice. Details opens a card with the explanation, the templates (the same element on many pages, fixed once in the template, fixed everywhere; Show example shows the close-up) and the pages with every element. Show on the page jumps to the Page view, Open in the page table to the Pages view, filtered on that rule.
  • Pages: every checked page with score, elements and To review, searchable. Filter All rules, Order with Lowest score first, Most critical first, By address or By host. Pages that could not be checked state the reason (Could not be checked: …).
  • Page: one page in detail, with the marked screenshot, the list of findings and the Comparisons section. Switch page jumps to another page, All pages back to the table. More in Comparison images.
  • History: Accessibility over time, every run a dot coloured by its score. Below are the runs with the same tools as in the audit's History: select, delete, leave out of the PDF.

In the WCAG matrix every criterion has a state: Passed, Failed, Needs review, Check by hand or Not applicable. Show criteria by state filters. Clicking a failed or doubtful criterion opens its findings, Show all criteria again removes the filter. Passed only means that no automatic rule found an error, not that the criterion is met.

What happens in the background

The check runs in a Chrome-family browser installed on your Mac: Google Chrome, Chromium, Brave or Microsoft Edge. WebDonkey does not download Chrome. On top comes the check module: a few npm packages (browser control and check rules) in fixed versions, which WebDonkey installs once into its own folder. It runs with Node.js.

Chrome loads every page like a normal browser, including images, scripts and fonts the page embeds from other providers. For local WebDonkey sites, Chrome trusts WebDonkey's certificates. A login from the audit entry applies to the check too. The images belong to the run and are deleted with it.

Free and Premium

The accessibility check is part of the SEO package.

Troubleshooting

When you start a run with accessibility, WebDonkey checks first (Checking whether Chrome and the check module are ready…). As long as something is missing, only SEO only can be started.

What you see Why What to do
No Chrome browser found No Chrome-family browser installed. Install Google Chrome, Chromium, Brave or Microsoft Edge.
Node.js missing The check module needs Node.js. Install Node.js on the Services page.
Check module not installed The npm packages are still missing. Click Install check module. That can take a minute.
The accessibility check could not run Something was missing during the run. The reason is shown, and below it the report of the last check that worked. Fix the reason and start Accessibility only.
Pages marked not checked The page did not finish in time or could not be loaded. Raise Time limit per page (s).

See also

Comparison images SEO package

The accessibility check takes pictures of the pages. They show where a problem spot sits and how the page looks to people who see differently or only use the keyboard. With the slider you lay the normal picture and the comparison picture on top of each other and see the difference directly.

Where to find it

  • In the report: Accessibility tab › Page view. At the top is the marked screenshot, below it the Comparisons section.
  • In the cards of the Findings view: close-ups of every element, and for templates via Show example.
  • For a single address: in the page inspector, Accessibility tab.

Which pages get pictures

Picture When it is made
Close-ups of the findings Always, for every element.
Screenshot of the whole page According to the Screenshots setting: Of every page, Only of pages with findings (default) or None (close-ups of findings only).
Comparisons (simulations, layout, keyboard) On the deep-checked pages: the home page and one page per template. Which groups is set by the Keyboard, Layout and Simulations switches.

The pictures belong to the run and are deleted with it.

How to do it

Read the marked page

  1. Open the Page view, for example via Weakest pages in the overview or Show on the page on a finding.
  2. Every element found carries a numbered frame in the colour of its severity. Click a frame (or press Enter on it) to select the element in the list next to it.
  3. Select an element in the list and its frame moves to the centre of the picture.
  4. Under Width you switch between the checked screen widths, under Zoom between Fit and 100 %.

Very long pages are cut off, and the picture then says so with Note:. Elements below the cut are still counted (Outside the picture: …). If the picture is missing at one width, that is down to the run's Screenshots setting.

Look at the comparisons

Under Comparisons you find the groups that were made for this page.

  • Simulations: the page's first screen at the main width next to six simulations: Red blindness, Green blindness, Blue blindness, No colour vision, Blurred vision and Low contrast vision. Clicking a tile opens the comparison with the normal view. Anything conveyed by colour alone stands out here.
  • Layout: each picture against its normal counterpart.
    • 320 px wide: like a phone or 400 % zoom. Nothing may need horizontal scrolling.
    • Text at 200 %: half the width, as with double-size text. Nothing may be cut off.
    • Text spacing: line, paragraph, letter and word spacing as WCAG 1.4.12 requires.
    • Forced colours: the system's contrast mode. Everything has to stay visible.
  • Keyboard: Tab order shows the page with numbered stops, connected by a line, the way the Tab key moves through the page. Next to it are the same stops as a list. Stops whose focus you cannot see (Focus not visible) and stops hidden by fixed content such as a header or a cookie notice (Covered) are marked. For elements without visible focus, With keyboard focus shows the element without and with focus.
  • Previous run: the same page from the previous run next to this run (Previous run, This run), each with its score. Below it lists what is New on this page and what is Fixed on this page. If the page was not part of the previous run, it says This page was not part of the previous run.

Compare with the slider

The comparisons under Layout and Keyboard and the opened simulations lay both pictures on top of each other with a dividing line between them: the normal picture on the left, the comparison picture on the right.

  1. Drag the line with the mouse, or use the arrow keys. With Shift it moves in larger steps, and Page Up, Page Down, Home and End work too.
  2. Under View you switch between Slider and Side by side. Side by side works better when the pictures differ in size, such as 320 px against the desktop page.

In the PDF

The accessibility chapter of the PDF shows the weakest pages with numbered elements, the simulations of the home page and close-ups of the most important problems (see Export reports).

Troubleshooting

What you see Why What to do
No screenshot of this page at this width (screenshot setting of the run). Screenshots was set to a sparing option. Change the setting and check again.
No comparison images for this page. The page was not deep-checked. Raise Pages with the deep check or check the page in the page inspector.
No element on this page can be reached with the Tab key. The page has no focusable elements, or all are locked out for the keyboard. Go through the page with the keyboard yourself.

See also

Report: Not crawled SEO package

The Not crawled tab lists the URLs the audit found but deliberately did not fetch, and gives the reason. Here you see whether important areas are missing because the budget was too small, a pattern excludes too much or robots.txt blocks them. A URL list has no such tab, because nothing is discovered there.

Where to find it

Report of an audit › Not crawled tab. The count on the tab is the total of URLs left out.

How to do it

  1. Pick All or a reason at the top. Each reason shows its count.
  2. Read the list: per URL the reason and, below it, the page it was found on ("found on …").
  3. If something is off, change budget, depth or exclusions in the Settings tab and run the audit again.

The reasons

Reason Meaning
robots.txt Blocked by the rules in robots.txt.
Excluded By a pattern under Do not crawl or Filter pages.
Parameters A URL with parameters that is skipped according to the URL parameters setting.
Too deep Beyond Max. click depth.
Filter trap Endless combinations of filter or sort parameters on the same path.
Link loop Relative links that keep nesting, such as /en/en/en/….
nofollow Only reachable via links with nofollow.
URL limit The URL budget ran out.
Other Everything else.

What happens in the background

Links to other domains are counted but never fetched, not even through a redirect. Whether an external link target is reachable is only checked with Check whether external links work, and then with a single request, without crawling the other site.

Troubleshooting

What you see Why What to do
Nothing left out The audit fetched every address in its area. Nothing.
The list of these addresses is no longer available. Run the audit again to create it. There is no stored list for this report any more. Run the audit again.
Many URLs under URL limit The website is larger than the budget. Raise the budget or exclude unimportant areas.

See also

Report: History SEO package

The History tab records every completed audit with its score and counters, so you can see whether your work on the website pays off. Here you can delete single or several audits and decide which audits the PDF report uses for its trend and comparison.

Where to find it

Report of an audit › History tab. Accessibility has its own history in the Accessibility tab, History view, with the same tools.

What you see

  • Score over time: a chart from the second audit on. Each dot is one audit, coloured by its score. A hollow dot is an audit that did not run to the end. The dashed lines mark 50 and 90.
  • Audits: one card per run, the newest on top and marked latest. Each card shows the date, the score, how the audit ended, the counters Pages checked, Errors, Warnings, Notices and the values for Content, SEO and Technical. On the right is the difference to the audit before (Score compared with the audit before).

Incomplete runs are marked as such, and a comparison with them is only a rough guide. How individual findings changed is shown in the Overview under Since the last audit.

How to do it

Leave an audit out of the PDF

The PDF is built on the newest audit, compares it with the one before and shows up to 24 audits in its trend. A run with wrong figures, for example during an outage, distorts that comparison.

  1. Turn off the PDF switch on the audit's card.
  2. The card now says not in the PDF. Trend and comparison in the PDF leave the audit out, in the app it stays visible.
  3. To bring it back, turn PDF on again.

The audit the PDF is built on is always included. Its switch is locked (The PDF is built on this audit; it is always included.).

Work on several audits at once

  1. Tick the boxes on the left of the cards, or Select all.
  2. At the top you see Selected: x with three buttons: Leave out of the PDF, Back into the PDF and Delete.

Delete audits

  1. Click the trash can on the card or, for several, Delete.
  2. Read the confirmation Delete audit? or Delete the selected audits (x)?. Everything the audit created is deleted: results, page list, resources, screenshots and the data of the accessibility check. Trend and comparisons are calculated without it afterwards.
  3. Confirm. This cannot be undone.

If the current audit is among them, the confirmation warns you: Overview, Issues and Pages stay empty until the next audit has run.

What happens in the background

The history lives in WebDonkey's database on your Mac. Leave out of the PDF only changes what the PDF export uses, it does not change the data. Deleting removes the stored data of the run.

Troubleshooting

What you see Why What to do
No history yet There is no completed audit yet. Run an audit.
A trend appears here from the second audit on. Only one audit has run. Run a second audit.
Deleting is locked, with the note Nothing can be deleted while an audit is running. A run is active. Wait until the audit is done, or stop it.
The PDF switch does not move The PDF is built on this audit. Nothing. It is always included.

See also

Audit settings SEO package

In an audit's Settings tab you decide how it crawls, what it leaves out and how gently it treats the server, plus keywords, additional pages and the accessibility settings. Changes apply from the next audit on. The current report stays as it is.

Where to find it

Report of an audit › Settings tab. You find the same crawl settings when creating and editing an audit under Advanced crawl settings.

How to do it

  1. Open the Settings tab.
  2. Change what you need. As soon as something has changed, Unsaved changes appears next to the buttons.
  3. Click Save. Afterwards it says Settings saved with the note that the changes apply from the next audit on.
  4. Discard changes restores the saved state.

Half-finished changes are kept if you briefly switch to another page.

Crawl settings

This section only exists for a crawl (Full audit or Section). At the top is the Filter pages row with Scan site (see Create an audit).

Setting Meaning Default
Crawl scope This subdomain only (exactly this host, with and without www treated the same), All subdomains of the domain (also shop., blog. and so on) or This directory only (the start URL and everything below it). Links to other domains are counted but never fetched. This subdomain only
Max. URLs crawled Upper limit of URLs, up to 500,000. Below it you see the longest the audit can take. 10,000
Max. click depth How many clicks from the home page the crawler goes at most, up to 100. Prevents endless subpages from filters, sort orders and calendars. 20
Do not crawl One pattern per line (see below). empty

Under Advanced:

Setting Meaning Default
Pause between requests (ms) Wait time between two requests, up to 10,000 ms. If robots.txt asks for a longer pause (Crawl-delay), that applies. 200
Parallel requests 1 to 4. 1
robots.txt Follow the rules for all crawlers (*), Follow the rules for Googlebot or Ignore robots.txt and nofollow. all crawlers
URL parameters Remove tracking and session parameters, Keep all parameters or Do not crawl URLs with parameters. remove tracking
Also ignore these parameters (one per line) More parameters the crawler removes from every URL, such as sort. empty
Identify as (user agent) WebDonkey monitor (honest) identifies with WebDonkey-Monitor/1.0 and a link to webdonkey.io, Like a browser (Chrome) like a Chrome browser on a Mac. WebDonkey monitor
Check whether external links work A single request per external URL, status code only. Other sites are never crawled. Leave it off if no requests should go to other websites. off
Check resources (images, scripts, stylesheets, fonts) Requests every file once after the crawl, see Resources. on

Patterns for Do not crawl

  • /es/ excludes /es and everything below it, but not /espresso.
  • * stands for any characters: /fr/*, *.pdf.
  • The query part (?…) only counts if the pattern contains a ?, for example /search?*.
  • Upper and lower case matter.
  • The home page is always crawled. If a pattern also matches the start address, the field warns you. Only the pages behind it are skipped then.

Excluded addresses are never fetched and do not count towards the limit. Filter pages is the more convenient way: scan the site and click paths away in the tree.

Accessibility

For a crawl, the Accessibility section sits below the crawl settings. Collapsed, it shows a summary such as "WCAG 2.2 AA · 1280, 390 px · deep check on up to 10 pages". The settings and their defaults are described in Check accessibility. For a URL list you change them with Edit on the card. Whether an audit checks accessibility at all is set there under What to check.

Keywords and pages

  • SEO keywords (comma-separated, optional): the audit checks whether each keyword appears in title, description, H1 and text.
  • For a crawl: Additional pages (one per line, optional). The crawler follows links from the start URL. Pages nothing links to, such as campaign landing pages, are only part of the audit if they are listed here.
  • For a URL list: Pages to check, one page per line. A path such as /checkout belongs to the audit's website, a full address is checked as typed.

What happens in the background

The settings are saved with the audit entry in WebDonkey's database. The running or last report does not change, only the next run uses the new values. The audit's password protection is kept when you save. You change it with Edit on the card.

Free and Premium

The settings are part of the SEO package. If an audit is locked after switching to Free, they cannot be changed.

Troubleshooting

What you see Why What to do
The settings could not be saved The reason is shown below, for example a missing SEO package. Fix the reason and save again.
Warning under Do not crawl A pattern also matches the start address. Narrow the pattern if you need the pages behind it.
The audit is throttled by the server Pause too short or too many parallel requests. Raise the pause, set Parallel requests to 1.

See also

Page inspector SEO package

The Page inspector fetches a single page once and analyses it in detail: status and redirects, timing, search result and social previews, findings, headings, keywords, links, images, resources, readability, structured data and response headers. In its second tab it checks the page's accessibility in Chrome. Nothing is saved.

Where to find it

  • From an audit: Pages tab › pick a page › Inspect. The page is fetched with this audit entry's settings, keywords and login.
  • Without an audit: Check a URL now on the SEO page or in the search (⌘K).

The inspector has two tabs: Page analysis and Accessibility.

How to do it

  1. Check or change the address under Address to inspect.
  2. Click Inspect. While the request runs it says Inspecting….
  3. Read the sections of the Page analysis from top to bottom.
  4. If needed, switch to the Accessibility tab and click Check accessibility.

The page analysis

Section What it shows
Status Status code, whether the page was reached directly or after redirects, Indexable with the reason if not, Canonical, Robots directives, Language and hreflang.
Timing To first byte, Download, Total, Size, Transferred and HTTP version.
Search result preview How title and description look in a desktop search result, with length in characters and pixels and the verdict Fits, Short, Gets cut off or Missing.
Social preview The preview for Open Graph (Facebook, LinkedIn, Messenger) and X. Copy the tags copies the tags.
Findings This page's findings with their severity, as in the audit.
Heading structure The outline of all headings, with notes on a missing or repeated H1 and skipped levels. Copy the outline.
Keyword density The most frequent terms with Count and Share. Under Words per term you pick 1 word, 2 words or 3 words.
Links Every link, filterable by All, Internal, External and nofollow.
Images Every image, filterable by Without alt and Without dimensions.
Resources The files the document names, by kind, including the files that block rendering.
Readability A readability index from 0 to 100, higher reads more easily, plus Words, Sentences, Words per sentence and the text share of the HTML. The formula follows the page's language.
Structured data The JSON-LD and microdata found.
Response headers Every header of the response. Copy all headers.

Long lists show a part first, and Show all x reveals the rest. Copy these addresses and Copy this table put a list on the clipboard. Open in browser opens the page.

The Accessibility tab

Check accessibility checks the address in Chrome against WCAG 2.2: automatic rules at every width, keyboard and focus, layout at 320 px and 200 % zoom, and how the page looks with colour vision deficiencies. This works with local sites too and takes one to two minutes.

  • Without an audit entry, the inspector uses the default settings (WCAG 2.2, level AA).
  • Via Inspect from an audit, that audit's accessibility settings and login apply. Nothing is saved in the audit.

You get the score (Accessibility), Checked address, Title, Language and Duration, the Page with markers at every Width, the Findings with Show places, what is To review by hand, the best practices, the number of passed and not applicable rules, and the Comparisons in the groups Colour vision and display, Layout and Keyboard (see Comparison images). Here too: Result of an automatic check. It does not replace a full audit under BITV 2.0 / EN 301 549.

What happens in the background

  • The page analysis fetches the page once and follows up to ten redirects. Nothing is saved.
  • When you check a public address, WebDonkey does not follow any redirect into your local network or onto this Mac, for safety. Local addresses such as shop.test, localhost or an address in your own network you check as usual.
  • The pictures of the accessibility check are deleted after one day.

Free and Premium

The page inspector is part of the SEO package.

Troubleshooting

What you see Why What to do
No answer: the host name could not be resolved (DNS). A typo, or the domain does not exist. Check the address.
No answer: the server refused the connection. No web server at this address. For local sites: is the site running?
No answer: the server took too long. Timeout. Try again later.
No answer: the secure connection failed (TLS certificate). The certificate is invalid. Check the site's certificate.
The redirects run in a circle and never arrive at a page. Redirect loop. Check the website's redirect rules.
Not fetched: the address points into a private network and was blocked for safety. A public page redirects into the local network. Check the redirect. Enter local addresses directly.
Chrome, Node.js or the check module missing The accessibility check needs them. Follow the note in the tab, for example Install check module.
The page did not finish in time. A slow page. Check again. For an audit, raise the time limit in its accessibility settings.
The site refused the login. Wrong credentials in the audit. Check user and password with Edit on the audit card.

See also

Check a URL now SEO package

Check a URL now examines a single address without creating an audit: One address, checked right away. Nothing is saved. That suits a quick check, for example after changing a page, or a page that belongs to no customer.

Where to find it

  • SEO page › top right Check a URL now.
  • Search (⌘K) › SEO: check a URL now. WebDonkey switches to the SEO page and opens the dialog.

How to do it

  1. Open Check a URL now.
  2. Enter the address under Address to inspect, such as https://example.com/page. Without a scheme, https is assumed.
  3. Click Inspect.
  4. The result appears in the page inspector: the Page analysis and, in the second tab, the Accessibility check.

Fields and options

Field Meaning
Address to inspect An address with http or https. Without a scheme, WebDonkey assumes https.
Inspect Fetches the page once and analyses it.

Without an audit entry, the default settings apply, with no keywords and no login. If you need an audit's settings, such as the password protection of a staging site, open the page there in the page table with Inspect.

What happens in the background

The page is fetched once, and the result only lives in the dialog. When you check a public address, WebDonkey does not follow any redirect into your local network or onto this Mac, for safety. Local addresses such as shop.test, localhost or an address in your own network you check as usual.

Free and Premium

The check needs the SEO package. Without the package the button is locked (Needs the SEO package).

Troubleshooting

What you see Why What to do
Enter an address first. The field is empty. Enter an address.
This is not a valid address. The input cannot be read as an address. Check the spelling, for example https://example.com/page.
Only http and https addresses can be inspected. Another scheme, such as ftp://. Enter the address with https://.
The page could not be inspected. The request failed, the reason is shown with it. See Page inspector.

See also

Export reports SEO package

You can save an audit's results as a file: as a designed PDF report for your customers, as the page table in CSV for your own analysis, or as the complete report in JSON. The PDF report can carry your own sender and, if the audit checks it, also covers accessibility.

Where to find it

  • In an audit's report at the top right under Export: CSV, JSON and PDF.
  • On the audit card: Save report as PDF (the icon with the downward arrow).

Exporting only works after the first audit: There is something to export after the first audit.

How to do it

Create a PDF report

  1. Click PDF in the report. The Create PDF report dialog opens.
  2. Under Contents, pick SEO (the SEO audit), Accessibility (the accessibility check) or Both in one PDF (cover with both scores, then both reports). If one of the two reports is missing, that choice is locked and the dialog says why.
  3. With your own sender: your company's logo and name on the cover and in the footer. It is on as soon as a sender is set and can be turned off for this report. If there is none yet, enter one via Edit sender (see Reports).
  4. Report for: the customer, for example Example Ltd. It appears on the cover and is remembered for this audit.
  5. Click Create PDF and choose where the file goes. For a large audit this takes a moment.

Afterwards WebDonkey names the file's location (PDF saved).

PDF from the card

Save report as PDF on the card creates the SEO report without asking. If a sender is set, the report carries it and the customer remembered for this audit. While it is being created the card shows Creating the PDF…, then PDF saved: with the path.

CSV and JSON

  1. Click CSV (Page table as CSV) or JSON (Whole report as JSON) in the report.
  2. Choose where to save.

The CSV file has one row per page with every value of the page table, the column names in the app's language. The JSON file contains the whole report.

Contents of the PDF report

SEO: cover with the score, Overview, the changes since the previous run, Findings in detail, Content, Technical, Pages with the most problems, the website check, History and the Appendix (run, crawl settings, what was not crawled, how to read the score).

Accessibility: what the check means (Result of an automatic check. It does not replace a full audit under BITV 2.0 / EN 301 549.), the score with the elements by severity, Compared with the previous run, WCAG criteria by principle, The most important problems with what to do and an example from the website, Template problems, The weakest pages with numbered elements, How others see the home page, To check by hand and About this check.

Which audits the trend and comparison use, you decide in the History.

What happens in the background

  • The PDF is created on your Mac, nothing goes over the network.
  • The report comes out in the app's language. For Chinese, Japanese and Korean it is created in English.
  • With a sender, your company name also appears as author in the PDF file's properties. Without a sender, the report carries the WebDonkey logo.

Free and Premium

Exports are part of the SEO package, and so is your own sender.

Troubleshooting

What you see Why What to do
Export buttons are grey There is no completed audit yet. Run an audit.
The PDF export failed Creating or saving failed, the reason is shown below. Read the reason, such as a write-protected folder, and export again.
This entry has no accessibility check yet. The audit has not checked accessibility yet. Run with accessibility, or pick SEO.
With your own sender cannot be ticked No company name is set. Edit sender.

See also

Cookie preferences

This website uses cookies to ensure the best experience possible. Your choice applies to webdonkey.io and the shop at shop.webdonkey.io. More information...

Technically required

Cookies required for this website to function:

Always on
WebDonkey
WebDonkey
Provider: BuI Hinsche GmbH, Neumarkt 7, 06712 Zeitz, Germany
Purpose: Your consent, colour scheme and language for website and shop, price switches; with wd_debug in the address, the measurement events in the developer console for troubleshooting
Cookies and storage: Cookie wd_consent on .webdonkey.io, shared with shop.webdonkey.io (12 months); cookies wd_theme and wd_lang on .webdonkey.io, shared with shop.webdonkey.io, only when you switch colour scheme or language yourself (365 days); localStorage wd:consent, wd:theme, wd:lang; sessionStorage wd:acc, wd:term, wd:debug (only with wd_debug in the address; until the tab closes)

Statistics

Shows us which pages and products people look at on webdonkey.io and in the shop, where visitors come from and how they get to a purchase (with order number, amount and products, without name or email address). Provider: Google. Transfer to the USA possible (EU-US Data Privacy Framework). Your choice applies to webdonkey.io and the shop together.

Google Tag Manager, Google Analytics 4
Google Tag Manager
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Loads the services you agreed to, here and in the shop. Sets no cookies of its own.
Cookies and storage: none
Privacy policy
Google Analytics 4
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Usage statistics: page views, clicks, scroll depth, sources, devices, load times; in the shop also basket, checkout, purchases, registration and sign-in
Cookies and storage: _ga, _ga_<ID> (2 years)
Privacy policy

Marketing

Measures whether our ads on Facebook, Instagram and TikTok lead to visits and downloads on webdonkey.io and to registrations and purchases in the shop, and builds audiences for ads. Providers: Meta and TikTok, with whom we are jointly responsible for this. With this consent Google may also set advertising cookies (_gcl_…). Transfer to the USA and other countries outside the EU possible. Your choice applies to webdonkey.io and the shop together.

Google Tag Manager, Meta Pixel (Facebook, Instagram), TikTok Pixel
Google Tag Manager
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Loads the services you agreed to, here and in the shop. Sets no cookies of its own.
Cookies and storage: none
Privacy policy
Meta Pixel (Facebook, Instagram)
Provider: Meta Platforms Ireland Limited, Merrion Road, Dublin 4, D04 X2K5, Ireland
Purpose: Ad measurement and target groups on Facebook and Instagram, also in the shop (basket, checkout, purchases, registration)
Cookies and storage: _fbp (3 months), _fbc (3 months, only if you arrive through an ad), fr on facebook.com (3 months)
Privacy policy
TikTok Pixel
Provider: TikTok Technology Limited, 10 Earlsfort Terrace, Dublin, D02 T380, Ireland
Purpose: Ad measurement and target groups on TikTok, also in the shop (basket, checkout, purchases, registration)
Cookies and storage: _ttp, _tt_enable_cookie (13 months)
Privacy policy