SEO mistakes that get Nepali websites penalized or ignored

This is the oldest mistake and it is still everywhere on Nepali business sites: 'We are the best trekking agency in Nepal. Our trekking agency in Nepal offers trekking in Nepal for trekkers who want to trek in Nepal.' Someone believed that sentence would help rankings. It does the opposite.

Google's spam policies name keyword stuffing as a practice that can lead to lower rankings or removal from results. Ranking systems do not need a term repeated, they use language models to understand a page from natural writing. A stuffed page reads as manipulative to both algorithm and visitor.

Recovery is mechanical: rewrite in plain language, use the keyword where it fits naturally (title, one H2, the opening paragraph), and use synonyms elsewhere. Sites fixed this way typically climb again within a few weeks of recrawling, because nothing was ever technically broken, the content was just unreadable.

This is the mistake we see most in Nepal specifically. An agency builds one template, a homepage, an about page, a services page, and reuses it for a dozen clients: swap the logo, the phone number, reword a paragraph. Sometimes the same agency runs several of its own 'lead generation' sites off the identical template.

Google's guidance on duplicate content is clear: near-identical pages across domains dilute which version gets shown, and can be treated as scaled content abuse if produced to manipulate rankings. The practical effect is usually not a manual action, it is that none of the near-identical sites rank well, because Google consolidates them or decides none is worth showing.

We have audited Kathmandu sites where the 'competitor' beating them was, unknown to the client, built by the same agency off the same template. Neither ranked as well as either could have alone.

Recovery means actually differentiating: real photos, real staff names, real pricing, real local detail. If you suspect your site shares a template with others, compare the raw HTML. Identical paragraph structure with swapped nouns is the giveaway.

Link schemes are named directly in Google's spam policies: buying or selling links that pass ranking credit, excessive link exchanges, links from low-quality directories or article farms built purely to manipulate rankings. Nepal has a small but active market for this, packages promising '500 backlinks' from directory submissions, guest post networks that publish anything for a fee, comment-spam link drops.

These links almost never help and often hurt. A sudden spike of low-quality links with no natural growth pattern is a strong spam signal, and can trigger a manual action for unnatural links, visible in Search Console. Even without a formal action, Google's algorithms simply do not count these links as trust signals, so you have spent money for nothing.

Recovery starts with an audit: pull your backlink profile in Search Console or a tool like Ahrefs, identify the spammy batch, use the disavow tool. If you have a manual action, disavow first, then file a reconsideration request. This can take weeks, so the real fix is never buying links at all. Earn a handful from real Nepali news sites or industry associations instead, one of those outweighs a hundred directory links.

Running English content through a translator and publishing it as Nepali, or generating pages at scale with an AI tool and publishing them unedited, both fall under what Google calls scaled content abuse: content produced to manipulate rankings rather than help a person, regardless of whether a human or a machine wrote it.

The tell is always the same: pages that could apply to any business in any city, generic paragraphs with no specific detail. A hotel site auto-translated from an English template, idioms meaning nothing in Nepali, is one example. So is a hundred 'best restaurant in [city]' pages generated for every district by the same prompt with the city name swapped in.

This does not usually trigger a manual action unless done at real scale. More often the page simply never ranks, or ranks briefly then falls away as helpful content systems catch up, because it adds nothing beyond what already exists. Recovery means rewriting with real, first-hand information, or removing and redirecting the page if it cannot be salvaged. Thin pages left live also drag down how the rest of the site gets evaluated.

Cloaking is showing search engines different content than you show visitors, for example serving a keyword-stuffed page to Googlebot while human visitors see something else. Hidden text is a lighter version: white text on white, text shrunk to one pixel, a keyword list stuffed into an off-screen div. Both are named in Google's spam policies as deceptive practices.

We still see this on older Nepali WordPress sites, left over from a theme or plugin an agency configured years ago, sometimes without the current owner knowing it is there. It reads as deliberate deception, one of the more likely triggers for an actual manual action rather than a quiet demotion.

Recovery: check your page source for text that does not appear visually, check whether your server sends different HTML to Googlebot than to a browser, and remove what you find. If Search Console shows a manual action, fix it, verify both now see the same page, then submit a reconsideration request explaining exactly what was removed. Reviewers want specifics, not a generic apology.

Google has indexed the mobile version of sites as the primary version for years now. If your desktop site is polished and your mobile site is an afterthought, tiny text, buttons a thumb cannot tap accurately, a menu that never opens, that broken experience is what Google is actually evaluating.

This is not usually a manual action, it is a straightforward case of being ignored rather than penalized. Most Nepali mobile traffic runs on mid-range Android over 4G slower than advertised, and a site taking eight seconds to become usable loses the visitor before ranking is even the deciding factor. Poor usability and slow loading correlate with high bounce rates, which feeds back into how the page performs over time.

Recovery: test the actual site on an actual mid-range phone, not a browser's device emulator. Check that tap targets are large enough to hit reliably, text is legible without zooming, forms work with a mobile keyboard, and the largest image loads quickly. Search Console's Core Web Vitals report shows which pages are struggling and why, page by page.