Checks
FreePages checks every website before a new version goes into the preview and before it goes online: build, content and links, external sources, open facts, required details for the legal notice and privacy policy, translations, accessibility and the display on narrow screens. Before uploading to a server, a full check with Lighthouse is added. The result is on the Checks tab in the menu.
What you do here
- Automatic checks: when Pages checks, how to check yourself and which browser Pages needs for it.
- Reading the result: understanding the summary, check parts and findings.
- What gets checked: every rule per check part.
- Full check with Lighthouse: the measurement before publishing.
Red, yellow, green
- Red: this must be fixed. The preview doesn't show a new version with red parts; it stays on the last checked one. After a change in the chat, Pages has the AI fix red findings itself. If that fails, Pages discards the change (What happens with a message).
- Yellow: the preview works, uploading to a server doesn't yet. Typical causes are open facts, missing required details, a missing domain, legal pages not yet confirmed, missing translations or no browser for the checks.
- Green: passed.
Pages only uploads a version to a server that has no red and no yellow parts and has passed the full check with Lighthouse. Yellow parts don't block the ZIP export.
Page layout
Open the Menu on the right and choose the Checks tab. The number on the tab counts the red check parts.
- At the top, the Check now and Full check with Lighthouse buttons.
- Below, while a check runs, the current step.
- A box with the summary and below it As of … with date and time.
- The list of check parts, each with a symbol and the number of its findings.
The bar
- Lighthouse mobile: performance at least 98, accessibility, best practices and SEO 100 each.
- No violations of WCAG 2.2 AA, checked at 390 and 1440 pixels wide.
- No overflow at 360 and 390 pixels wide.
Check parts, summary and findings appear in the language the interface was set to when the check ran (Language).
Free and Premium
Checks and the full check are fully included in Free.
Automatic checks Free
The quick check runs by itself whenever something on the website changes. It rebuilds the website and checks everything except Lighthouse. You can start it yourself at any time too, for example after confirming the legal pages.
When Pages checks
- after every change from the chat, as the Final check step,
- after you save something under Facts, including the Contact form section,
- after you change a text on the Texts tab or by clicking it in the preview,
- after you remove languages or switch the default language under Edit website (if a language is added, Pages first suggests translating in the chat),
- when you go back to an earlier version: with Undo, Redo or in the history,
- before a ZIP export, if something has changed since the last check,
- when you click Check now on the Checks tab.
Before uploading to a server, the full check with Lighthouse runs instead of the quick one.
The checkbox I have read the legal notice and privacy policy and the details are correct. under Facts doesn't start a check. Click Check now afterwards and the yellow note about it disappears.
How to start it yourself
- Open the Menu on the right and choose the Checks tab.
- Click Check now.
- The title bar shows Checking …, the tab shows the current step, such as "Building the website", "Checking content and links", "Checking accessibility and width in the browser" or "Accessibility checked at 390 px".
- The tab then shows the new result (Reading the result).
The buttons are locked while Pages is working on the website and for archived or locked websites. If there hasn't been a check yet, the tab says No checks yet. They run automatically after every change: accessibility, mobile layout, content and links.
What happens in the background
- Pages builds the website as a new version and checks it. Meanwhile the preview keeps showing the last checked version.
- If the new version has no red parts, it becomes the version of the preview, the ZIP export and the local test in WebDonkey. Yellow parts don't hold it back.
- For accessibility and width, Pages starts a browser invisibly in the background and opens the pages there through the local preview. The check runs entirely on your Mac.
- Pages saves the result in the website's folder. When you open the website again later, it is still there.
Browser for the checks
Pages checks accessibility, width and Lighthouse in a real browser. It looks for Google Chrome (in the Applications folder or your own Applications folder), Chromium, Google Chrome for Testing and Microsoft Edge, in that order. Which one Pages found is shown under Settings, Technology, Browser for checks (Technology).
Without a browser, Pages skips these checks and shows the yellow part Accessibility and width with the note "Chrome not found, browser checks skipped". Without a browser there is no Lighthouse measurement either, and the website can't be uploaded to a server.
Troubleshooting
| What you see | Why | What to do |
|---|---|---|
| The Legal notice and privacy policy part stays yellow although you confirmed. | The checkbox doesn't start a new check. | Click Check now. |
| Yellow part Accessibility and width | Pages can't find a browser. | Install Google Chrome and check again. |
| The Build part is red. | The website couldn't be built. | Ask the AI in the chat to fix the error, or go back with Undo. |
| Check now is greyed out. | Pages is working, or the website is archived or locked. | Wait until the run is finished, or reactivate the website. |
See also
Reading the result Free
The Checks tab shows the result of the last check: a summary at the top, below it every check part with its findings. At a glance you see whether the website is ready to publish and what is still missing.
Where to find it
Open the Menu on the right and choose the Checks tab. As soon as check parts are red, the tab itself shows a number: the count of red parts.
The summary
The box at the top is green when the website is ready to publish, red for findings that must be fixed, and neutral otherwise. It contains one of these sentences:
- "3 findings need to be fixed: …", followed by the names of the red parts,
- "Technically fine. Still missing before publishing: …", followed by the names of the yellow parts,
- "All quick checks passed. The full check with Lighthouse runs before publishing.",
- "All checks passed."
Below it, As of … shows date and time of the check; after a full check with the addition with Lighthouse.
The check parts
Below the summary there is one row per part with a symbol: a green tick for passed, a yellow warning triangle for notes, a red sign for errors. The number on the right counts the findings. Clicking the row expands and collapses it; red parts are already open. Pages shows up to 30 findings per part. Rows without findings can't be expanded.
| Check part | Appears | Findings are |
|---|---|---|
| Build | always | red |
| Content, links, external sources | always | red, single notes yellow |
| Open facts | always | yellow |
| Legal notice and privacy policy | always | yellow |
| Languages | for websites with several languages or missing texts | yellow |
| Accessibility (WCAG 2.2 AA) | when Pages finds a browser | red |
| Display on narrow screens | when Pages finds a browser | red |
| Accessibility and width | only when there is no browser | yellow |
| Lighthouse (mobile) | only after a full check | red |
If the build already fails, the check ends after the Build part. What each part checks in detail is described in What gets checked.
Reading findings
Most findings start with the page concerned, for example "/contact/: Link to /prices leads nowhere" or "/: Image without alt text (…)". Accessibility findings also name the width in pixels, the rule and the affected spots on the page. For the Lighthouse (mobile) part there is one line per page with four values in the order performance / accessibility / best practices / SEO, for example /: 99 / 100 / 100 / 100.
What to do
- Red: ask the AI in the chat to fix the findings. The easiest way is to copy the finding into your message. Or go back to the version before the change with Undo.
- Yellow for Open facts or Legal notice and privacy policy: add the missing facts and confirm the legal pages.
- Yellow for Languages: have the missing texts translated, for example with "Translate the website" in the chat, or fill them in yourself on the Texts tab.
- Yellow for Accessibility and width: install Google Chrome (Automatic checks).
- All green except Lighthouse: start the full check with Lighthouse. If you upload straight to a server, Pages runs it by itself.
See also
What gets checked Free
Each check part has fixed rules. Red findings must be fixed before a version goes into the preview. Yellow findings only hold up uploading to a server. Here are all rules, in the order in which Pages checks the parts.
Build
The website must build without errors. If the build fails, this part is red and lists the build's error messages. The other checks are skipped then.
Content, links, external sources
On every page of the finished website, Pages checks directly in the HTML, without a browser:
| Rule | Finding |
|---|---|
| a page title with at most 60 characters | red |
| a description with 120 to 160 characters, for pages that search engines should index | red |
| a language attribute for the page | red |
| exactly one main heading | red |
| alternative text on every image | red |
| nothing from external servers: no scripts, stylesheets, fonts, images, media or embeds, not via the design either | red |
| no iframes, because external embeds need consent | red |
| no links leading nowhere within the website | red |
| one link each to the legal notice and the privacy policy | red |
| with several languages: a language switcher in the header that links to all languages of the website | red |
| internal links with a trailing slash (without one, every visit costs a redirect) | yellow |
| no placeholders for missing details in the text | yellow |
Open facts
Yellow as long as questions under Facts are open. Each finding names the question. How to answer them is described under Facts.
Legal notice and privacy policy
Yellow as long as something is missing that the legal notice and privacy policy need:
- the website's domain,
- name and address of the hosting provider for the privacy policy,
- the required details of your business, depending on the legal form, for example name, address with a five-digit postcode, email address, a second fast way to get in touch (phone or contact form), authorised representatives and register entry,
- your confirmation that you have read the legal notice and privacy policy and the details are correct.
Which details are required for your legal form is described under Business.
Languages
This part exists for websites with several languages and whenever texts are missing in a language. It is yellow as long as
- texts in a language aren't translated yet (another language's text shows there for now), or
- pages don't have their search engine description in all languages yet.
The finding names the language and the number of texts and suggests writing, for example, "Translate the website" in the chat. You can also fill in missing texts yourself on the Texts tab.
Accessibility (WCAG 2.2 AA)
Pages opens every page in a browser, at 390 and 1440 pixels wide, and checks it with axe against WCAG 2.0, 2.1 and 2.2 up to level AA plus axe's best-practice rules. Areas that fade in on scrolling are shown right away for this. Expandable areas are checked again in their expanded state. Every violation is red and names width, page, rule and up to three affected spots.
Display on narrow screens
Every page at 360 and 390 pixels wide: nothing may stick out over the edge of the screen. Content in its own swipeable area, such as a wide table that itself fits on the screen, doesn't count as overflow. Pinned elements don't count either. Every overflow is red and names the width and up to three elements that stick out.
Accessibility and width
This yellow part only exists when Pages can't find a browser. The two browser checks and Lighthouse are skipped then (Automatic checks).
Lighthouse (mobile)
Only with the full check, see Full check with Lighthouse.
See also
Full check with Lighthouse Free
The full check does everything the quick check does and also measures every page with Lighthouse in the mobile view. It usually takes one to two minutes, longer with many pages. Only a version that passed the full check can be uploaded to a server.
Where to find it
- On the Checks tab in the menu, with the Full check with Lighthouse button.
- In the Publish website dialog on the ZIP for your host route: the Full check with Lighthouse button sits next to Export ZIP as long as the last check wasn't a full one.
- By itself before uploading to a server with Check and publish, if the current version hasn't been fully checked and cleared yet (What must be ready first).
How to do it
- Open the Menu on the right and choose the Checks tab.
- Click Full check with Lighthouse.
- The title bar shows Full check …. The tab lists the steps, including "Lighthouse is running (takes a while)" and for each page a line such as "Lighthouse /: Performance 99, Accessibility 100, Best Practices 100, SEO 100".
- Afterwards, As of … below the summary carries the addition with Lighthouse, and the list contains the Lighthouse (mobile) part.
Thresholds
| Category | at least |
|---|---|
| Performance | 98 |
| Accessibility | 100 |
| Best Practices | 100 |
| SEO | 100 |
If a page falls below in any category, the Lighthouse (mobile) part is red. The finding names page, category, value and threshold and up to four reasons from Lighthouse.
Reading the values
When you expand the Lighthouse (mobile) part, there is one line per page with four numbers in the order performance / accessibility / best practices / SEO, for example /: 99 / 100 / 100 / 100. The row can be expanded even when everything passed.
What happens in the background
- Lighthouse runs in an invisible browser on your Mac and measures the local preview, not the website on the internet.
- It measures the pages that search engines should index. Pages that explicitly shouldn't be indexed are left out.
- Performance varies by a point or two on a Mac. If it is below 98, Pages measures the page once more and the better value counts.
- Every later check replaces the result. After a change, the new version needs a new full check. When uploading to a server, Pages does that by itself.
Ready to publish
The website is ready only when no part is red or yellow and Lighthouse has passed. The summary box is then green and says "All checks passed."
Troubleshooting
| What you see | Why | What to do |
|---|---|---|
| The Lighthouse (mobile) part is missing after the full check. | Pages found no browser; the yellow part Accessibility and width is shown. | Install Google Chrome (Automatic checks). |
| Performance below 98 | Lighthouse found something slowing the page down. Up to four reasons are in the finding. | Ask the AI in the chat to fix the reasons given and check again. |
| After a change, the addition with Lighthouse is gone again. | A quick check replaced the result. | Run the full check again or upload straight away. |
| The buttons are greyed out. | Pages is working, or the website is archived or locked. | Wait until the run is finished. |