Get started →

Home / Guides / Why MCM child sites get rejected, and what to fix

● MCM

Why MCM child sites get rejected, and what to fix

Updated 16 November 2026 · 3 min read · By Arslan Mehdi

Accepting an MCM invitation is the easy part. After that, Google reviews the child account and each site added to it. Some sites don't pass. A rejection is frustrating, but it usually points at something fixable. These are the causes we see most, roughly in order of how often they come up.

Thin, copied or unfinished content

This is the big one. Google wants sites that offer readers something of their own.

  • Copied or lightly rewritten content from other sites.
  • Auto-generated pages with little human effort: mass-produced articles, scraped feeds, doorway pages.
  • Sites still being built: placeholder text, empty categories, broken menus.
  • Too few pages to judge the site.

The fix is unglamorous: publish useful, original pages, remove the filler, and make the site look finished.

Policy problems

Google's publisher policies apply to every MCM child site. Common issues:

  • content Google won't monetise, such as adult material, dangerous products or misleading claims;
  • copyrighted material you don't have the rights to, including pirated media or downloads;
  • pages built to trick people into clicking, such as fake download buttons.

Our policies overview lists the areas to review. If a section of the site is the problem, removing or reworking it is often enough.

Traffic quality

If a large share of the traffic looks invalid, expect trouble. Bought traffic, bot-driven visits, and heavy data-centre or proxy traffic all count against you. See signs of bot traffic and the risks of buying traffic.

Fixing traffic takes longer than fixing content. Stop the paid sources first, then give your numbers time to settle.

Setup and ownership issues

  • The domain doesn't match. The site added must be the one you actually run, at the domain that serves the ads.
  • ads.txt is missing or wrong. Use the exact lines your partner gave you.
  • The site isn't reachable. Login walls, geo-blocks or bot protection that blocks Google's crawler can stop the review.
  • History. Accounts or sites with past policy problems can face a harder review.

What "good enough" looks like. Publishers often ask for a word count or a page count that guarantees approval. There isn't one. What reviewers respond to is a site that clearly exists for its readers. In practice that tends to mean a working navigation, an about page that says who runs the site, a way to contact you, a privacy policy, and articles that answer a question better than a search snippet would. A small site that does those things well usually stands a better chance than a large one full of filler.

A practical order to fix things

  1. Read the rejection reason carefully. It's not always detailed, but it usually narrows things down.
  2. Check the site is reachable, finished and on the right domain.
  3. Review content against the policies and remove anything doubtful.
  4. Look at traffic sources and switch off anything paid or suspicious.
  5. Fix ads.txt.
  6. Ask your partner how and when to request another review. Don't resubmit an unchanged site.

Preventing the next rejection

Once a site has passed, the work isn't finished. Sites can be reviewed again, and problems that appear later can still cause trouble. A few habits help:

  • Keep publishing properly. A site that was good at review time and then fills up with thin pages is heading back to the same problem.
  • Check new traffic sources before you scale them. A new referral partner or campaign can change the quality of your visits overnight.
  • Review user-generated content. Comments, forums and uploads are your responsibility for policy purposes.
  • Keep ads.txt current after every partner change or migration.
  • Watch the policy notices in your Google account and act on them quickly. Small issues fixed early rarely become account problems.

When you add new sites to an existing network, apply the same checks before they're submitted. One weak site added in a hurry can create problems for the people who manage the rest.

What a good partner does here

A partner should check sites before sending invites, not after Google says no. At Bidora we look at content and traffic quality first, and we'll tell you straight if a site isn't ready. That saves everyone a rejection.

Talk to us about joining Bidora MCM. We send Manage Account invitations, you choose our share starting at 8%, and IVT Shield is included. Start on the Get started page or email partnership@bidora.one.

Ready when you are

Tell us about your site. We'll take it from there.