Soloware
中EN
Contact

Services

Three tiers. The difference is whether we tell you, or we do it.

Technical audit

NT$ 25,000one-time

We inspect, prioritise and explain. You or your engineers do the fixing.

  • Site-wide crawler visibility scan (not just the homepage — templates and representative inner pages)
  • Three-layer block check: edge, robots.txt, meta
  • Structured data inventory and gap list
  • Fix list ordered by impact, each with its evidence source and an effort estimate
  • 60-minute walkthrough call, recorded for you
  • No implementation
  • No content writing
Ask about this tier

Fix engagement

NT$ 90,000one-time from

The audit, then we implement the fixes and verify them in your environment.

  • Everything in Technical audit
  • Implementation: server-side rendering, crawler access, structured data output, heading and section structure, response speed
  • Delivered as pull requests; your team reviews before merge
  • Before/after scan comparison report
  • One regression check within 30 days
  • No ongoing content programme
  • No promise of specific rankings or citation rates
Ask about this tier

Retainer

NT$ 45,000per month from

For sites that keep shipping. This debt comes back, especially after a front-end rewrite.

  • Monthly site-wide rescan and regression report
  • Pre-launch checks for new pages and templates
  • Structured data maintained as the product changes
  • Content structure guidance (answer-first, section length, data density)
  • Cancel any time, no lock-in
  • No paid media
  • No PR or media placement
Ask about this tier

Questions

How long does an audit take?

Five working days. The site-wide scan runs on day one; the rest is manual verification. Automation can only tell you something looks wrong — deciding what is a deliberate policy and what is an actual mistake takes a person. We would rather take two more days than put a false positive in a report.

How do you work with our engineering team?

We deliver pull requests; your team reviews before merge, and we never touch production directly. Access to a fork is enough if you prefer. Every PR carries a before/after scan comparison so the reviewer can see exactly what the change fixes.

Our site is a SPA. Do we have to rewrite it?

Usually not. On most React or Vue projects you only need server-side rendering or prerendering on the pages that should be citable — product pages, articles, documentation. Dashboards and interactive views can stay exactly as they are; AI crawlers were never going there. A full rewrite is a last resort, not a starting point.

How soon will we see results?

Crawler access and structured data are verifiable the moment they are fixed — run the scan yourself and you will see it. But being cited is not a timeline we control: it depends on re-crawling, and since half of all citations come from content under 13 weeks old, your publishing cadence matters too. Anyone who gives you a specific number of days is making it up.