Verify a footer that is actually live

Start with the page response

Open the public website and inspect its page source. Find the actual footer links and their destinations in the HTML. Repeat with JavaScript disabled to confirm the content is visible and usable.

An empty mount, a script containing serialized HTML, or a successful account connection does not establish a crawlable footer.

Compare the current publication

Check the footer against the currently published version in your workspace. Confirm the expected website binding, link labels and destinations. A footer can be visible while still showing an older publication.

1Footer uses public HTML checks when verifying supported automatic delivery. Search engines decide how they crawl and rank a page; HTML verification does not promise indexing, backlinks or Domain Rating growth.

Check the pages visitors use

• A real included page contains the expected footer.
• A real excluded page stays clear.
• Missing or private pages are not counted as successful included-page tests.
• Navigation between included and excluded routes applies the same rules.
• Desktop and mobile layouts show one usable footer without overflow.

Keep the states distinct

These describe different parts of delivery. Review the website result before assuming a provider response means the footer is visible.

• Connected: an account or integration is linked.
• Published: a footer publication or site update has been accepted.
• Verified: the checked public output matches the expected publication.
• Paused: footer delivery is intentionally disabled.
• Needs attention: access, conflicting changes or an incomplete check needs resolution.