MiyaIP / SEO
Growing MiyaIP’s organic search presence. Clicks up 75.2%.
Meridian combined content strategy, page optimization, and implementation support to expand MiyaIP’s search presence. Organic clicks rose 75.2% across two 28-day windows.
Continue reading- Google organic clicks
- +75.2%
- Google search impressions
- +376.2%
- organic clicks in the latest 28-day window
- 4,300
Google Search Console · Web search · August 1–28 vs September 26–October 23, 2026. Each window covers 28 days of whole-site search data.
MiyaIP serves people choosing proxy products and people configuring them in desktop, mobile, and developer workflows. Its search content spans product pages, pricing, free tools, comparisons, and English and Chinese tutorials. The engagement began around August 2026.
The Challenge: Reach potential customers as they choose and configure proxies
Our strategy connected three search needs: comparing proxy products, completing a setup, and solving a connection problem. We combined improvements to existing product and tool pages with new tutorials, linking the content to relevant product and pricing pages so readers could move from a search question to an informed choice.
We used Search Console queries to identify where search visibility needed clearer page content. Recommendations included more precise product naming and billing information, a prominent free-query entry for NSLookup, and links from the Chinese static-residential guide to setup tutorials and pricing. The aim was to help searchers recognize the right page and find a useful next step.
Recurring audits compared the published site with the deliverables. For tutorial images, feedback identified the page, section, affected diagram or screenshot, and expected correction. The next weekly plan combined this follow-up list with the next set of page copy, metadata, and illustrations.
The Goal: Connect search discovery with product selection and setup
Give each product selection, setup, and troubleshooting question a useful page.
Review the live implementation and carry outstanding page improvements into the next delivery cycle.
The Solution
Meridian combined search analysis, content strategy, page optimization, and implementation support. We worked with the client’s team on copy, metadata, illustrations, and product links, then reviewed the published pages and carried outstanding improvements into the next round.
- Build content around product decisions and real use
- Improve pages already appearing in search
- Follow the strategy through to the live site
- Engagement began around August 2026
Diagnosis and page decisions
- Build content around product decisions and real use
- We developed content for the questions people ask before and after choosing a proxy: which product fits, how to configure it, and how to verify the connection. Product explanations, comparisons, tools, and tutorials gave each question a relevant destination. We supported this strategy with a weekly cadence of 10 page-metadata optimizations and 20 blog articles.
- Improve pages already appearing in search
- We used Search Console queries to identify where search visibility needed clearer page content. Recommendations included more precise product naming and billing information, a prominent free-query entry for NSLookup, and links from the Chinese static-residential guide to setup tutorials and pricing. The aim was to help searchers recognize the right page and find a useful next step.
- Follow the strategy through to the live site
- Recurring audits compared the published site with the deliverables. For tutorial images, feedback identified the page, section, affected diagram or screenshot, and expected correction. The next weekly plan combined this follow-up list with the next set of page copy, metadata, and illustrations.
Implementation and review
01 · Week seven · search review
Product, tool, and guide improvements
The plan covered mobile, residential, and datacenter proxy pages, NSLookup, Free Proxy List, the Chinese static-residential guide and pricing page, and HTTP versus SOCKS5 content. It specified naming, headings, descriptions, billing and session information, usage prompts, and relevant product links, alongside a new cloud-phone proxy setup guide.
02 · Week eight · tutorial delivery
Clash setup across desktop and mobile
The delivery update covered Clash integration entry points, platform-specific setup tutorials, and related page improvements. Modification locations were marked against the existing site, new content was distinguished from revisions, and illustrations and an asset package were included for implementation.
03 · Week nine · previous-week audit and next plan
Specific image corrections and the next page batch
The week-eight audit identified tutorial diagrams and screenshots cropped to 16:9, hiding steps, labels, or interface edges. It listed correction locations across Windows, Android, Mihomo, Mac, and Clash Verge guides, recommending original image proportions on desktop and mobile. The week-nine plan also supplied copy, metadata, and illustrations for Web Data, Integrations, Developer Center, and request-configuration and troubleshooting content.
Results
In the supplied Search Console export, whole-site organic clicks rose from 2,455 to 4,300 and impressions from 16,889 to 80,426 between the early-August and latest available 28-day windows. That is 1,845 more clicks and 63,537 more impressions.
Search performance and measurement
In the supplied Search Console export, whole-site organic clicks rose from 2,455 to 4,300 and impressions from 16,889 to 80,426 between the early-August and latest available 28-day windows. That is 1,845 more clicks and 63,537 more impressions.
Organic clicks
+75.2%- August 1–28, 2026
- 2,455
- September 26–October 23, 2026
- 4,300
Search impressions
+376.2%- August 1–28, 2026
- 16,889
- September 26–October 23, 2026
- 80,426
- Broader reach and higher clicks, with a lower CTR
- Aggregate CTR moved from 14.54% to 5.35% as impressions grew faster than clicks. The totals include brand and non-brand queries across the whole site. The export records search performance during the engagement; it does not isolate the contribution of an individual page or establish lead or revenue growth.
- Delivery cadence and implementation status
- The weekly 10 metadata optimizations and 20 blog articles describe the engagement’s delivery cadence. Audit findings and page plans retain their recorded status: an image correction request is a follow-up task, and a supplied new-page plan is not treated as a confirmed launch. Later plans are not used to explain earlier search changes.
What this means for similar projects
MiyaIP’s case shows how we approach SEO for a technical product: understand how customers search, connect content with product decisions, and work with the client’s team to improve the live experience. During the engagement, the latest 28-day window reached 4,300 organic clicks and 80,426 impressions, with further work focused on turning that visibility into useful product visits.




