OpenACAI

Website Standards

Website standards

How OpenACAI keeps the public website useful, safe, accessible, and ready for serious review by visitors, partners, funders, search engines, and Google Ad Grants.

Help-first navigation

The first paths point to resources, forms, urgent help, contact, and programs instead of making visitors decode organization language.

Substantial public content

Mission, programs, help guides, resources, forms, research, transparency, privacy, and donation pages are built as HTML pages, not thin PDF-only stubs.

Privacy-safe measurement

Events track broad actions such as prints, donation clicks, and contact success. Message text, search text, phone numbers, names, and emails are not sent to analytics.

Accessible workflows

Pages use semantic headings, visible labels, keyboard-friendly controls, contrast-aware styles, printable content, and no required audio.

Security and caching

Public pages can be cached. Contact and account pages use no-store behavior. WordPress noise, public user lists, XML-RPC, and empty public utility pages are restricted.

Grant account readiness

The site supports mission-specific landing pages, sitelink-worthy destinations, meaningful conversion paths, and clear nonprofit details.

Ad Grants readiness

Built around the review checklist, then pushed further.

OpenACAI cannot force an approval decision, but the public website can remove the usual weak points: thin pages, vague mission language, broken donation paths, empty sections, unclear conversions, and pages that fail on phones.

Review packet

The pages a reviewer should be able to trust quickly.

Google still controls eligibility and account approval. OpenACAI can control the evidence on the site: clear mission, real service pages, no empty public sections, working calls to action, privacy-aware measurement, and useful pages that match the ad intent.

Mission and activities

Our Mission, program pages, help guides, resources, forms, games, evidence, volunteer, donate, and transparency pages explain what OpenACAI does and who it serves.

Substantial original content

Core information is written as HTML pages with local help steps, form worksheets, research context, and program boundaries instead of thin pages or PDF-only navigation.

Navigation and working paths

Primary paths lead to Resources, Forms, Contact, Donate, Volunteer, Evidence, Accessibility, and Transparency. Old empty public utility pages redirect away from dead ends.

Speed, mobile, and HTTPS

Public pages are HTTPS, Cloudflare-cached where appropriate, responsive, and backed by machine-readable status contracts for app and monitor checks.

Donation and conversion quality

Donation, volunteer, contact, resource export, and form worksheet events are meaningful actions. Page views and search text are not treated as conversions.

No excessive commercial behavior

The site does not run AdSense, affiliate traffic pages, unrelated commerce, or misleading medical/game claims. Program limits are published beside the features.

Google review areas

What this site is built to satisfy.

Google makes the final eligibility decision. OpenACAI can still keep the website aligned with the published website and Ad Grants account policies.

Public pages that should be strong landing pages
  • Resources
  • Forms Library
  • Help Guides
  • T.E.C.H.
  • GAMHON Games
  • Evidence and Research
  • Volunteer
  • Donate
  • Transparency
  • Contact
Ad Grants campaign guardrails

Use specific phrases tied to real pages and local services. Avoid single-word or overly broad keywords, and keep conversion tracking limited to meaningful actions.

Recommended first sitelinks
  • Find local resources
  • Forms library
  • Volunteer
  • Donate
  • Evidence and research
  • Contact OpenACAI
Recommended first campaign groups
  • Local resource help
  • Forms and benefits preparation
  • Technology and document help
  • Volunteer and donation support
  • GAMHON and partner evidence
Ongoing maintenance

Review resource listings, check broken links, purge stale cache, keep donation/contact paths working, and remove empty public pages before submitting or expanding grant campaigns.