A 90-Day Plan to Improve SEO for Your Nepal Business
Use an existing baseline and audit to move through six accountable phases: access, foundations, priority pages, supporting content, authority and measurement.
Before you begin
This plan starts after a baseline and prioritised audit. If you have not established those, run my 60-minute SEO audit first. Ninety days is a management cadence: long enough to ship connected work and short enough to review honestly. It is not a promise to improve Google ranking in Nepal by a particular date.
How I use this roadmap
This is an execution sequence, not another complete explanation of SEO in Nepal. Use my complete guide to SEO in Nepal for the wider principles, and the interactive SEO checklist for Nepali businesses when you need a reusable task tracker. A day-one plan chooses immediate actions; this roadmap governs what follows once evidence exists.
I assign one accountable owner to every deliverable. The owner may do the work or coordinate a developer, writer or operations colleague, but cannot be “the team”. Keep one decision log with the URL, evidence, change, date, owner and validation method. That discipline matters whether the hypothetical business serves Kathmandu local search, runs a clinic in Lalitpur, operates a workshop in Bhaktapur or sells tours from Pokhara.
Weekly deliverables and owners
Copy these rows into the project sheet. Replace the blank with one name and agree the review date before work begins.
| Week | Deliverable | Owner |
|---|---|---|
| 1 | Access register, baseline export and conversion definitions | ________ |
| 2 | Technical evidence log and blocked-priority-page fixes | ________ |
| 3 | Search-intent clusters and first keyword map | ________ |
| 4 | Approved page map, templates and measurement checks | ________ |
| 5 | First priority commercial page and local profile corrections | ________ |
| 6 | Remaining priority-page improvements and structured data validation | ________ |
| 7 | First supporting resource and internal-link pass | ________ |
| 8 | Second evidence-led content improvement and orphan-page check | ________ |
| 9 | Review process, conversion-path test and legitimate mention list | ________ |
| 10 | Outreach or partnership round and conversion friction fixes | ________ |
| 11 | Quality assurance crawl and priority-page scorecard | ________ |
| 12 | Search Console comparison and consolidation decisions | ________ |
| 13 | Day-90 review and approved next-quarter backlog | ________ |
Days 1-15: evidence and technical access
I begin by proving access: domain and hosting, CMS, Search Console, analytics, tag manager and, where relevant, Google Business Profile Nepal ownership. Export the current query, page, country and device data before changing anything. Define conversions as actual calls, forms, bookings or orders, then test them. Do not treat sessions as a business outcome.
Next, turn the audit into a technical SEO Nepal issue log. Inspect priority URLs for status, indexability, canonical choice, robots controls, rendering, sitemap inclusion, mobile usability and Core Web Vitals. Use Google's Search Console and PageSpeed Insights as primary evidence. Fix an accidentally blocked service page before polishing low-value metadata. The phase ends with working access, a frozen baseline and an ordered defect list, not a generic “health score”.
Days 16-30: page map and foundations
Group real queries and customer language by intent, then assign each group to one existing or planned URL. My keyword mapping process is deliberately spreadsheet-based: query cluster, intent, page, business value, current evidence, owner and status. Research English, Devanagari and natural Romanised Nepali where customers use them, but do not produce a separate thin page for every wording.
Approve the site map before writing. Decide which services, categories, products, locations and guides deserve a page, which overlap should merge and which URLs should remain unindexed. Establish title, H1, canonical, navigation and conversion patterns for each template. Validate analytics again after template work. The deliverable is an agreed page system that makes Nepal business SEO maintainable, not a large speculative keyword list.
Days 31-45: priority pages and local profile
Improve the pages nearest to revenue first. Make the offer, audience, location or delivery coverage, process, evidence, limitations and next action clear. Write distinct titles and descriptions, use helpful headings, add genuine images where available and ensure contact routes work on a phone. Add structured data only when it describes visible facts, following Google's structured data guidance.
For an eligible local business, correct the profile name, category, address or service area, phone, hours and website. A hypothetical Lalitpur clinic should publish the location and appointment facts it can verify; it should not create near-identical Kathmandu and Bhaktapur pages merely to reach wider searches. Use my local SEO Nepal service approach for deeper profile and location work. The aim is accurate local representation, not a guaranteed map position.
Days 46-60: content and internal links
Now fill the most important information gap revealed by the map. A hypothetical Pokhara tour operator might clarify a real route, season or booking question; a Kathmandu professional firm might explain scope, documents or fees. Publish only material someone can review for factual accuracy. One first-hand answer that supports a commercial page is more useful than a weekly quota of interchangeable posts.
Link every supporting page to its mapped service, category or product page with descriptive anchors. Add links back where the resource genuinely helps a buyer, and repair orphan pages and broken destinations. Internal linking should reflect decisions, not repeat the same exact phrase mechanically. Re-crawl the changed area and inspect the rendered links before calling the phase complete.
Days 61-75: authority and conversion
Create a routine for requesting honest reviews from all eligible customers without incentives or review gating. Respond without disclosing private details. List legitimate suppliers, associations, partners, events and publications that could accurately mention the business, then propose something useful: original expertise, a resource, an event page or corrected attribution. Avoid bulk backlink packages and read Google's spam policies before outreach.
Test the entire conversion path on a real mobile device: result to landing page, call or form, confirmation and internal follow-up. Remove unnecessary fields, clarify response expectations and ensure the responsible person receives the enquiry. Authority without a usable next step wastes attention; conversion work without relevant discovery has too little input.
Days 76-90: measurement, consolidation and next quarter
Re-run the same crawl, URL samples and scorecard. Compare Search Console periods carefully, noting launches, outages, festivals and campaigns. Look for relevant query-page relationships, indexation changes, clicks and conversions; average position is contextual, not a fixed rank. A short period may show no reliable movement. Record that honestly rather than claiming causation.
Improve pages gaining relevant impressions but failing to satisfy the click or conversion. Merge overlap, fix regressions, update the map and carry unfinished dependencies forward explicitly. End with a next-quarter backlog ranked by impact, confidence, effort and dependency. That is how an SEO strategy for Nepali businesses compounds: measured decisions, not a ceremonial monthly report.
Risks and dependencies
| Risk or dependency | Early response | Owner |
|---|---|---|
| CMS, domain or profile access delayed | Escalate ownership in week 1; do not build plans on screenshots | ________ |
| Developer capacity unavailable | Separate template blockers from editorial work and book release dates | ________ |
| Business facts or legal claims unapproved | Name the subject reviewer before drafting | ________ |
| Tracking unreliable | Test events and preserve a manual enquiry log | ________ |
| Search demand differs from assumptions | Use query and customer evidence; revise the map | ________ |
| Seasonality distorts comparison | Annotate context and compare like periods where possible | ________ |
Local and ecommerce variants
Local business: prioritise profile ownership, category, hours, directions, service boundaries, local pages with unique operational value, calls and bookings. A hypothetical Bhaktapur repair business may need precise coverage and landmark directions; it does not need dozens of city-swap pages. Reviews and consistent business information belong in weekly operations.
Ecommerce: prioritise category architecture, product uniqueness, variants, filters, canonical rules, stock, NPR pricing, delivery coverage, payment, returns and order tracking. Measure product views, basket actions and completed purchases. A store serving all Nepal should not pretend to have locations in Kathmandu, Lalitpur or Pokhara. Both variants follow the same phases; their priority URLs and conversions differ.
The low-budget version
If time or money is tight, restrict the quarter to five assets: verified Search Console and conversion tracking, the top three commercial pages, one correct Business Profile where eligible, one useful supporting answer and the internal links connecting them. Use free Google tools and a spreadsheet. Ask a developer only for confirmed technical blockers that prevent priority pages from being crawled, indexed, loaded or used. The full technical SEO Nepal service is appropriate when diagnosis or implementation exceeds in-house capability.
Do not spread a small budget across daily posts, multiple city pages and low-quality links. Concentration produces a cleaner test and leaves maintainable assets even when rankings do not move within the quarter.
Day 0 and day 90 scorecard
| Measure | Day 0 | Day 90 | Evidence |
|---|---|---|---|
| Priority URLs indexable and canonical | ___ / ___ | ___ / ___ | Search Console and URL inspection |
| Priority intents assigned to one page | ___% | ___% | Keyword map |
| Critical technical blockers open | ___ | ___ | Issue log |
| Templates passing Core Web Vitals | ___ / ___ | ___ / ___ | Field data where available |
| Profile facts verified | ___ / ___ | ___ / ___ | Website and Business Profile |
| Relevant non-branded impressions and clicks | ___ / ___ | ___ / ___ | Search Console |
| Tested qualified conversions | ___ | ___ | Analytics and enquiry log |
The scorecard can show whether implementation and visibility changed; it cannot prove that every movement came from one action. “Improve Google visibility in Nepal” is a valid direction. A guaranteed ranking or conversion number is not.
What not to do during the 90 days
- Do not change URLs, titles and site structure simultaneously without a record and redirect plan.
- Do not publish city pages that merely replace Kathmandu with Lalitpur, Bhaktapur or Pokhara.
- Do not buy bulk links, reviews or engagement.
- Do not add structured data for reviews, products or locations that are not visibly true.
- Do not chase every warning in an automated tool before fixing business-critical access and page gaps.
- Do not report a ranking screenshot as proof of Nepal business SEO success.
- Do not continue content production when approval, accuracy or internal linking cannot be maintained.
Frequently asked questions
Will this 90-day SEO plan guarantee rankings in Nepal?
No. Ninety days is a planning cadence, not a ranking promise. Search engines, competitors, demand, recrawling and implementation quality remain outside any consultant's full control. The plan guarantees only a clearer sequence, ownership and review point.
What must be complete before starting the plan?
Complete a baseline and prioritised audit first. You should know the business goal, priority page types, current Search Console and analytics state, major technical blockers, conversion definitions and who controls the website and Business Profile.
Can a small Nepal business follow the plan without paid SEO tools?
Yes. A small site can make substantial progress with Search Console, Analytics, Business Profile, PageSpeed Insights, spreadsheets and manual result checks. Paid tools mainly increase speed and coverage; they do not replace judgement or implementation.
Should a local business and an ecommerce store use the same roadmap?
Use the same six-phase sequence but change the priority assets. A local business emphasises its Business Profile, location facts, reviews and calls or bookings. An ecommerce store emphasises categories, products, filters, stock, delivery, returns and completed orders.
How much content should be published during the 90 days?
Publish only what the evidence and available review capacity support. Strengthening one priority service or category page and one genuinely useful supporting answer can be better than producing many overlapping articles. Quality, distinct intent and internal links matter more than a quota.
How should progress be measured at day 90?
Compare the same scorecard used at the start: access, indexation, priority-page coverage, mapped queries, local accuracy, Core Web Vitals status, relevant impressions and clicks, and tested conversions. Record what changed without presenting short-term movement as proof of causation.
What happens after day 90?
Keep proven maintenance work, finish valuable dependencies and choose the next quarter from evidence. Improve pages earning relevant impressions, resolve remaining technical constraints, expand only into supported demand and stop activity that produced no useful learning or business value.
Turn your audit into an owned 90-day backlog
Send me the audit, three priority URLs and the conversion that matters. I will help separate the next quarter's work from the tasks that can wait.