Publisher identity
Name the person, business, nonprofit, or editorial project responsible. If using a public pen name for legitimate safety reasons, use it consistently and do not invent credentials.
Google does not list either page as a standalone universal checkbox on its general AdSense eligibility page. Both are still strongly recommended because they make ownership, purpose, expertise, and accountability visible to readers and reviewers.
Google's current general AdSense eligibility page does not explicitly say that every website must have a URL named “About” and another named “Contact.” It asks whether the publisher has original high-quality content, complies with policies, controls the site and its source, and meets the account age requirement. Therefore, calling both pages universally mandatory misstates the published checklist.
However, you should create both pages for nearly every independent publisher site. They answer basic trust questions that anonymous, automated, deceptive, or unfinished sites often leave unresolved. Their absence can weaken the overall application even though Google does not publish a rule saying “missing Contact page equals automatic rejection.”
Google Search's current people-first content guidance asks whether content provides background about the author or publishing site, specifically mentioning links to an author page or a site's About page. It strongly encourages accurate authorship where readers expect it. This is Search quality guidance, not a secret AdSense scoring formula, but it provides first-party evidence that transparent publisher identity and background matter.
A Contact page serves a different function: accountability. It gives readers, rights holders, sources, customers, advertisers, and regulators a practical route to reach the publisher. Google Publisher Policies prohibit misrepresenting or concealing material information about the publisher, creator, purpose, or content. A Contact page does not alone prove identity, but a real, working route is more credible than an anonymous site with no recourse.
The safest conclusion is simple: not explicitly universal, but strongly recommended and usually worth treating as part of a complete AdSense-ready site. Build them for users, accuracy, and accountability, not as empty pages written for a crawler.
| Item | Evidence level | Why it matters | Important qualification |
|---|---|---|---|
| Original, high-quality content | Explicit eligibility requirement | Google's eligibility page requires unique, interesting, high-quality content. | No trust page compensates for copied, thin, or policy-violating main content. |
| Policy compliance | Explicit eligibility requirement | The site must comply with AdSense Program and Publisher Policies. | Requirements continue after approval. |
| Site ownership and source access | Explicit eligibility requirement | The publisher must control the site sufficiently to connect AdSense. | An About page is not ownership verification. |
| About page | Strongly recommended trust signal | Explains publisher identity, purpose, authorship, experience, and editorial background. | Google's general AdSense eligibility page does not list it as a standalone universal checkbox. |
| Contact page | Strongly recommended accountability signal | Provides a real path for questions, corrections, rights complaints, and business inquiries. | A phone number or home address is not universally required by AdSense. |
| Privacy disclosures | Policy and law dependent | Google's policies require specified disclosures concerning data collection, sharing, cookies, and advertising. | Content must match actual services and visitor jurisdictions. |
| Terms, disclaimer, editorial policy | Depends on site activities | Clarifies use, risk, commercial relationships, standards, and boundaries. | Not every simple blog needs the same legal-page bundle. |
Do not turn “strongly recommended” into “optional and useless.” A fire extinguisher is not the engine of a car, but that does not make it decoration. About and Contact pages solve real trust and accountability problems even when they are not the main content Google monetizes.
Most ranking pages call About, Contact, Privacy, Disclaimer, and Terms pages “mandatory” without distinguishing a published Google policy from conventional publisher practice. Some claim approval is nearly automatic once these links appear in the footer. That overpromises and can lead site owners to ignore the main reason applications fail: weak or noncompliant content.
At the other extreme, some discussions say About and Contact pages do not matter because a site can occasionally be approved without them. That mistakes possibility for good preparation. A reviewer examining an unfamiliar site reasonably wants to know who operates it, why it exists, and whether anyone can be reached when content is wrong or infringing.
Competitor templates are another problem. They encourage vague text such as “We are a team of passionate experts dedicated to providing the best information” even when the site is run by one anonymous affiliate publisher. A truthful one-person page is stronger than a fictional team. Generic trust language can actively undermine credibility when author pages, domain history, social identities, and content reveal inconsistencies.
This guide separates four questions competitors blend together: what AdSense explicitly states, what Google recommends for trustworthy content, what privacy or local law may require, and what a serious publisher should do even without a named checkbox. That produces a more accurate and useful answer.
The About page should help an unfamiliar reader answer “Who publishes this, who is it for, and why should I trust its work?” It is not a corporate autobiography and should not be padded to an arbitrary word count.
Name the person, business, nonprofit, or editorial project responsible. If using a public pen name for legitimate safety reasons, use it consistently and do not invent credentials.
Explain what the site publishes, who it serves, and what readers should expect. A defined editorial mission makes unrelated search-first content easier to spot and remove.
Describe work, education, lived experience, testing, research, or enthusiast knowledge that genuinely supports covered topics. Match credentials to claims.
Explain reporting, testing, sourcing, reviews, updates, or corrections when those processes affect trust. Link to a detailed editorial policy if needed.
Disclose parent organizations, owned products, sponsorship models, or material conflicts when readers might otherwise mistake marketing for independent publishing.
Link to author profiles, editorial standards, corrections, disclosures, contact details, and a few representative resources. Avoid a footer-link dump.
Do not invent a newsroom, office, awards, clients, licenses, professional status, or review board. Do not use AI-generated headshots to imply real employees. Do not call every writer an expert. Do not claim “unbiased” while hiding ownership or compensation that materially affects recommendations.
Avoid publishing private information merely to appear legitimate. AdSense does not universally require your home address, personal telephone number, birth date, identification number, or payment details on the About page. Publish the business information required by laws that apply to you, but do not expose sensitive personal data without reason.
The About page explains the publication. An author page explains a contributor. A one-person blog can combine them if the result is clear. A multi-author publication should usually maintain both: a site-level mission and ownership page plus individual biographies linked from bylines.
A Contact page should be functional, safe, and specific. It is not enough to install a form that silently sends messages to an abandoned mailbox. Test the entire path as a logged-out visitor and confirm delivery.
Provide a form, role-based email address, ticket system, or legitimate business contact appropriate to the site. A professional domain email is helpful but not an explicit AdSense requirement.
State which site, publisher, company, or team receives the message. This matters when one operator owns several websites or brands.
Explain how to report factual errors, copyright issues, privacy requests, accessibility problems, advertising, partnerships, or general questions. Route sensitive complaints appropriately.
State support hours or an honest response window if useful. Do not promise 24/7 support when nobody monitors the inbox.
Explain or link to how form data is used, stored, protected, and shared. Mention anti-spam or form providers where relevant to your privacy disclosures.
Show a clear success or error message. Preserve form labels, keyboard access, contrast, and validation. Never collect more personal information than needed.
For many small publishers, yes: a working email address with context can provide meaningful contact. A form can reduce casual address harvesting but introduces delivery, spam-filter, JavaScript, consent, and accessibility failure points. Choose the route you can maintain reliably. You can also show a form and a fallback email.
Google's general AdSense eligibility guidance does not state that every website must publish a phone number or street address. E-commerce, financial, regulated, incorporated, or locally governed businesses may have separate consumer-information obligations. Follow applicable law and professional advice. Do not publish a home address merely because an SEO checklist told you to.
Use these as structures, not copy-and-paste final text. Replace every bracketed item with true, specific information. Delete sections that do not apply.
[Site name] helps [specific audience] with [topic or outcome]. We publish [formats] based on [first-hand experience, testing, reporting, research, or professional process].
The site is operated by [person or legal organization]. [Short, verifiable background explaining relevance]. We created the site because [people-first reason].
Our content process includes [testing/sourcing/review/update method]. When a page contains affiliate links, sponsorship, or a material relationship, we disclose it [where/how]. Readers can report errors through [corrections/contact route].
Start with [two or three useful section links]. Learn more about our [editorial policy], [disclosures], or [contact process].
Contact [site or publisher name] about [general questions, corrections, rights, privacy, accessibility, business inquiries].
Email [role-based address] or use the form below. Include the relevant page URL when reporting an error or rights concern. Do not send passwords, payment information, identification documents, or other sensitive data through this form.
We usually review messages within [honest timeframe]. For privacy requests, see [privacy link and instructions]. For copyright reports, include [information you reasonably need].
[Form fields: name or chosen identifier, email, subject, message, optional page URL, consent/notice where required]
Keep the visible page human. Legal details can be linked where appropriate, but the main copy should help a reader understand and reach the publisher. A wall of boilerplate is not a substitute for identity or accountability.
| Site type | About page emphasis | Contact page emphasis | Additional trust page |
|---|---|---|---|
| Personal blog | Creator identity, intended audience, lived experience, themes, and editorial purpose. | Working email or form, corrections, collaborations, and privacy-safe boundaries. | Affiliate disclosure when monetized commercially. |
| Multi-author publication | Ownership, leadership, editorial mission, standards, and links to author profiles. | Editorial, rights, advertising, privacy, and correction routes. | Editorial and corrections policies. |
| Affiliate review site | Testing method, ownership, expertise, funding, and ranking independence. | Product corrections, brand inquiries, and reader feedback. | Affiliate and review methodology disclosures. |
| E-commerce plus content | Business identity, product focus, location or service market, and brand story. | Customer service, returns, orders, privacy, and business inquiries. | Shipping, returns, and consumer terms. |
| Tool or SaaS site | Operator, tool purpose, methodology, data sources, limits, and security posture. | Technical support, bug reports, privacy, security, and billing routes. | Terms, privacy, and methodology. |
| Health, finance, or legal site | Exact qualifications, reviewer roles, ownership, editorial process, and boundaries. | Corrections, professional inquiries, privacy, and urgent-use limitations. | Editorial review, disclaimers, and corrections. |
| Forum or UGC community | Operator, community purpose, moderation philosophy, and governance. | Abuse, safety, copyright, moderation appeals, and privacy reports. | Community rules and moderation policy. |
| Pseudonymous creator | Consistent public identity, honest reason where appropriate, experience, mission, and accountability without fake biography. | Role-based email or form that protects private identity while remaining reachable. | Editorial standards and disclosure of material conflicts. |
Transparency does not require doxxing yourself. Publishers may have legitimate safety, employment, cultural, or political reasons to use a pen name or protect a home address. Use a consistent public identity, describe experience truthfully, provide a working contact route, and avoid claims that require credentials you refuse or cannot verify.
A business can use a registered office, service address, or role-based inbox where lawful and appropriate. A solo publisher can use hello@domain.com rather than a personal mailbox. Do not claim a mailbox, virtual office, or coworking address is a staffed headquarters if it is not.
Names, email addresses, IP addresses, message contents, uploaded files, anti-spam scores, and analytics can be personal data. Collect only what is necessary. Secure transmission with HTTPS, restrict administrator access, set a retention period, keep plugins updated, and explain relevant processing in the Privacy Policy.
Third-party anti-spam tools may set cookies or transmit visitor data. Document actual providers and configure consent where required. Test that privacy controls do not make the form impossible to submit and that blocked scripts produce a useful fallback.
If the site is directed to children or invites health, legal, financial, or crisis disclosures, ordinary contact forms may be inappropriate. Minimize collection, publish clear limitations, use suitable safeguards, and obtain professional legal or privacy guidance for the jurisdictions involved.
A one-person site repeatedly says “our expert editorial team” without naming anyone. Use honest singular language or identify actual contributors.
“We provide high-quality information on many topics” explains neither audience, purpose, experience, nor editorial value.
Degrees, licenses, awards, clients, or years of experience are claimed without accurate context and conflict with author biographies.
The form shows success but email never arrives, SMTP fails, CAPTCHA blocks submission, or the inbox is not monitored.
A social profile can supplement contact, but accounts can disappear, require login, or fail to support rights and privacy requests.
A simple question form demands a phone number, address, company size, budget, and marketing consent without necessity.
About, footer, Privacy Policy, author pages, and domain branding name different operators because templates were copied.
The About page claims independence while the site owner sells the ranked product or receives compensation without disclosure.
Long boilerplate pages are published while articles remain copied, thin, unsafe, or inaccessible. Approval depends on the whole site.
Decide which person, legal entity, nonprofit, or editorial project is responsible and represent it consistently.
State the audience, covered topics, formats, and people-first reason for publishing.
Describe only relevant, accurate experience and qualifications. Avoid vague expert labels.
Describe testing, sourcing, editorial review, updates, AI assistance, or corrections when readers would care.
Reveal owned products, sponsors, affiliate models, and relationships that affect how content is understood.
Use a form, email, or support channel that somebody checks and can secure.
Provide routes or instructions for corrections, copyright, privacy, accessibility, abuse, and commercial questions as applicable.
Request only necessary fields and link the contact process to accurate privacy information.
Submit while logged out on mobile and desktop, confirm validation, delivery, reply behavior, and error handling.
Add crawlable footer or header links and resolve duplicate or broken legacy URLs.
Ensure names, ownership, addresses, emails, policies, bylines, and branding do not contradict each other.
Do not stop at trust pages. Review main content, policies, archives, navigation, traffic, mobile experience, and technical access.
They can fix missing transparency and accountability, but they rarely solve a rejection alone. If the site contains copied posts, mass-generated summaries, prohibited content, deceptive navigation, invalid traffic, inaccessible pages, or little original value, adding two footer links does not address the core problem.
After rejection, review the site's main templates and purpose. Improve or remove low-value pages, verify media rights, clean categories and search results, identify authors, repair navigation, test the mobile experience, investigate traffic, and ensure AdSense can access the canonical domain. Then make About and Contact pages accurate reflections of the improved publication.
Use our AdSense rejection guide and low-value content guide to diagnose problems beyond trust pages.
AdSense Audit is the #1 AdSense audit tool for site owners preparing to apply or reapply. It checks for missing or weak publisher identity, About and Contact accessibility, policy-page consistency, content quality, navigation, crawlability, and other technical or trust risks.
The audit helps distinguish a missing-page problem from a sitewide value problem. That matters because polishing a Contact form is wasted effort when hundreds of thin pages or a broken canonical setup are the real blockers.
No independent tool can guarantee Google's decision. AdSense Audit provides a practical, prioritized view of preventable weaknesses so you can submit a more credible publisher site.
Run My AdSense AuditGoogle's general eligibility page does not list it as a universal standalone checkbox. Google's helpful-content guidance does identify site and author background, including an About page, as information that supports trust. It is strongly recommended.
The general eligibility page does not explicitly list one as universal. A working contact route is strongly recommended because it demonstrates accountability and supports questions, corrections, privacy, and rights issues.
It may be possible, but their absence can make an unfamiliar site harder to trust. Adding them does not guarantee approval when main content or policies remain weak.
AdSense does not universally require every publisher to display a home address. Publish business details required by applicable law, but protect unnecessary personal information.
Yes for many sites if it works, identifies the recipient, handles data appropriately, and is monitored. Test it logged out and provide a fallback when practical.
A consistent pen name can protect privacy. Remain truthful about experience and relationships, provide a working contact route, and do not invent credentials or a fictional team.
You do not need to maximize ads on trust and utility pages. If ads appear, keep them separate from forms, contact links, navigation, and buttons. Many publishers choose a cleaner ad-light or ad-free layout.
Privacy disclosures can be directly relevant to Google policies and applicable law because advertising, analytics, forms, and cookies involve data. About and Contact pages serve different trust and accountability functions.
No. They improve transparency but do not transform copied, thin, mass-generated, or unhelpful articles into original publisher content.
No third party controls Google. AdSense Audit identifies preventable issues and helps prioritize a stronger application.
Policies and interfaces can change. Recheck official documentation before applying.
Google AdSense eligibility requirementsGoogle Publisher PoliciesGoogle AdSense Program policiesGoogle people-first content and authorship guidanceGoogle required content for privacy disclosuresGoogle: Connect your site to AdSense