Donation and action-page performance
Evidence required: page-performance data for the donation, volunteer, event, contact, biography, and major policy templates; error logs; form-completion testing; and a record of material releases that changed these pages.
Pass or fail: pass when critical journeys load reliably on representative devices, forms complete without avoidable errors, and the team can distinguish page-speed issues from form, script, or hosting failures.
Fail when users encounter recurring slowdowns, broken submissions, rendering faults, or unowned performance regressions. Severity: critical when a failure blocks a donation, volunteer registration, event lookup, press resource, or other campaign-critical action.
Owner: technical lead with digital operations. Corrective action: reduce avoidable script and media weight, fix blocking errors, test third-party embeds, and prioritize the pages tied to real campaign actions.
The source previously cited a 30-50 percent bounce-rate range for slow donation pages; because no supporting source URL is included, treat that as historical context rather than a campaign benchmark. Validation step: rerun device and form tests after deployment and compare the same page under similar conditions.
Secure transport and access controls
Evidence required: valid HTTPS delivery, current certificates, restricted administrator access, backup procedures, and documented ownership for hosting and domain changes.
Pass or fail: pass when all important pages load securely and the campaign can identify who can change the site, domain, or hosting. Fail when browsers warn users, mixed content breaks page behavior, or access is shared informally without accountability.
Severity: critical. Owner: technical lead or qualified security provider. Corrective action: enforce secure delivery, remove insecure resources, tighten permissions, rotate credentials when roles change, and document recovery procedures.
Validation step: inspect the live site from representative browsers and verify that critical campaign paths remain secure after redirects and embeds load.
Mobile usability for campaign traffic
Evidence required: device analytics, mobile rendering tests, tap-target checks, form tests, and page-speed evidence for the pages most likely to receive event or news traffic.
Pass or fail: pass when mobile users can read, navigate, submit forms, watch or access media, and reach the intended next step without layout or performance failures. Fail when important content is hidden, forms are unusable, or navigation blocks completion.
Severity: high. Owner: technical and design owners. Corrective action: simplify responsive layouts, compress appropriate assets, remove blocking interface patterns, and test on devices that reflect actual campaign traffic.
The source previously stated that over 70 percent of political searches occur on mobile during live events; no supporting source URL is embedded here, so validate device share with the campaign's own analytics. Validation step: compare live mobile analytics and task completion after the corrective release.
Crawlable campaign architecture and sitemap coverage
Evidence required: crawl results, sitemap contents, indexation reports, canonical settings, robots directives, and an inventory of policy, biography, endorsement, event, press, and action pages.
Pass or fail: pass when priority public pages are reachable through internal links, technically indexable where intended, and represented consistently in site architecture. Fail when important pages are orphaned, blocked unintentionally, duplicated without a clear canonical strategy, or missing from the site's navigable structure.
Severity: high. Owner: SEO lead with technical implementation support. Corrective action: repair crawl paths, remove accidental blocks, clarify canonical targets, update the sitemap, and connect durable pages with descriptive internal links. Validation step: recrawl the live site and confirm the intended public URL is the one search systems can discover.
Broken links and error-page control
Evidence required: a crawl report, server logs, internal-link inventory, and a list of URLs changed by campaign launches, event expiration, policy revisions, or redesigns.
Pass or fail: pass when important internal links resolve to current destinations and intentionally removed pages have an appropriate redirect or useful error experience. Fail when users repeatedly reach a 404 response from navigation, policy links, media coverage, or campaign emails.
Severity: high for high-traffic or campaign-critical destinations; lower for isolated obsolete URLs with no meaningful use. Owner: technical lead with content owner. Corrective action: update internal links at the source, redirect only where a genuinely relevant replacement exists, and keep error handling useful rather than forcing every removed URL to the home page. Validation step: recrawl and manually test the highest-value changed URLs.
Structured data accuracy
Evidence required: the markup present on candidate, event, article, organization, or other eligible pages; the visible page content it describes; and validation against current Google documentation.
Pass or fail: pass when markup is syntactically valid, represents visible content accurately, and uses supported properties for the page type. Fail when markup invents facts, describes hidden content, or is added solely to promise a rich result.
Severity: medium unless incorrect markup also reflects inaccurate public information. Owner: SEO lead with technical implementation and communications review. Corrective action: remove unsupported claims, align markup with visible content, and validate against current documentation.
Validation step: test the live page after deployment and verify that the structured data remains accurate when the underlying campaign information changes.