Why Google rejects a store with no privacy, returns or contact pages

What the error means

Merchant Center and ad platforms expect a store to present as a real business: a reachable contact channel, a privacy policy, terms, a returns and refund policy and, for stores, shipping information. Missing or unreachable trust pages are a documented cause of account-level and item-level rejections.

Why Google rejects it

Shopping puts a stranger’s money ahead of the goods. The policies are the store’s written promise of what happens after payment, and their absence signals a store that cannot be held to its word. Reviewers and automated checks look for the pages, and they count only when a visitor can actually reach them.

How to fix it

1. Publish the five pages: privacy, terms, contact, returns/refund and shipping. Store platforms ship templates — fill in your real legal entity, addresses and timelines.
2. Link every one of them in the site footer. A policy page nobody can reach does not count — reviewers and crawlers look there first.
3. Remove template placeholders. A "123 Fake Street" contact block or lorem-ipsum terms page reads as worse than none.
4. Make the values real and consistent: the return window stated on the page must match what you actually honour, because a mismatch is its own misrepresentation problem.

Common causes

Contact details are absent or incomplete

A contact form alone may not make it clear who operates the store or how a customer can reach the business. Google's editorial guidance gives missing contact details as an example of insufficient information. Check the public contact page and Merchant Center business details together for a real email, phone, or other supported contact method and consistent identity.

Return or refund terms are missing

A returns page that exists but omits eligibility, timeframe, or refund handling leaves customers unable to understand what happens after a purchase. Google identifies missing, unclear, or hard-to-find return information as a concern. Read the page as a shopper and ensure it describes actual terms rather than an unedited template.

Policy pages are not reachable from storefront

A page can be published but buried behind checkout or an account login, and footer links can still point to an old slug. Test each policy link from the public home and product pages. A crawler or reviewer must reach the policy without your admin session.

Business identity conflicts across surfaces

A store name, legal entity, address, or phone can differ between the site and Merchant Center. A legitimate business may use a trading name, but the relationship should be clear and the supplied information should be accurate. Check account verification and public contact details for stale addresses or inconsistent names.

Template or placeholder content remains

Sample policy copy, fake addresses, empty pages, and demo footer links can make a store look unfinished or misleading. Google lists templated content, placeholders, broken links, and unclear customer information in its editorial guidance. Review the site on mobile and follow every footer link as a new visitor would.

Fix it on your platform

On Shopify

1. Review Settings > Policies and replace generated or sample language with the store's actual privacy, terms, shipping, and refund or return terms. Confirm each policy page is published and viewable publicly.
2. Add policy, contact, and about links to the storefront footer menu using the current navigation or theme editor. Open the live site in a private window and test every link from a product page.
3. Check Store details and contact channels in Shopify admin, then compare the legal business identity and contact information with Merchant Center. Keep any public trading name understandable in relation to the account name.
4. Remove theme demo blocks, placeholder addresses, and empty policy sections. Test the cart and checkout as a visitor, since broken purchase flow can compound trust concerns.

On WooCommerce

1. Create public privacy, terms, shipping, return/refund, and contact pages with real details. In WordPress, set the privacy page under Settings > Privacy and assign the terms page in WooCommerce settings if the checkout uses one.
2. Add the relevant pages to the footer through Appearance > Menus or the block theme's footer template part. Check that the page URLs are current and do not redirect to the home page.
3. Compare the site's business name and contact details with the Merchant Center business information and verification records. Correct the source data instead of hiding a mismatch with more copy.
4. Remove sample pages and placeholder policy text, then test the public site and checkout without being logged in. Check caching or maintenance plugins that can show visitors a different site.

On other platforms

1. Use the builder's page editor and navigation or footer controls to publish the policies and contact page. Ensure the pages are public, linked sitewide, and use the live custom domain rather than a preview URL.
2. For Wix, BigCommerce, or Squarespace, use the platform's current business details and policy settings where available, then check the rendered public page to confirm the saved content appears.
3. On custom sites, create stable policy URLs, link them in a sitewide footer, and ensure they return accessible pages with descriptive titles and real terms.
4. Across any platform, make the business identity, contact routes, return timelines, shipping terms, and checkout behavior consistent with Merchant Center and the product offer.

How to confirm it is fixed

1. Open the home page and a representative product page in a logged-out private window. Follow footer links to contact, privacy, terms, shipping, and returns; confirm none require an account or lead to placeholders.
2. Compare legal business name and contact information on the site with Merchant Center business details and identity verification. Correct discrepancies at their source.
3. Read the return and shipping pages against checkout behavior. Confirm timelines, fees, countries served, and contact instructions describe what customers can actually do.
4. Run the trust check from outside your network and clear missing or unreachable page findings before requesting a review.
5. In Merchant Center, review the precise issue and request a review only after changes are live. A review evaluates the current store; it is not a guarantee that the account will be approved.

A worked example

Hypothetical case: a specialty food shop receives a website needs improvement warning. The footer contains a Privacy link and a Returns link, but the latter points to a deleted page, while the contact page has only a form and no visible business email. The store also displays a different business name than the verified Merchant Center account. The owner publishes accurate return and shipping terms, fixes the footer destination, adds a monitored customer contact channel, and updates the account information to match the real business. They test the site logged out and request a review after the pages are publicly reachable.

Other errors like this