Fivetran is hiring a Sales Director to build its enterprise base "within various regions in Japan" and a Partner Sales Manager in Tokyo. The Japanese site is already built: 1,681 URLs in the sitemap, including 784 connector pages and 34 case studies, each with a canonical and hreflang. But robots.txt says "Disallow: /ja", so Google cannot crawl any of them. A Japanese data engineer searching "Salesforce データ連携" never sees the Japanese page the company paid to translate.
First action
Check in Search Console whether any /ja URL is indexed, then delete the two Disallow lines.
How to measure it
Japanese organic clicks
- Now
- –
- Target
- from near zero to 2,000 a month
- By
- 90 days
Steps
Confirm intent
Ask web and legal whether the block was deliberate; if not, remove it.
Web Strategy & Optimization Lead 1 day
Edit robots.txt
Drop "Disallow: /ja" and "/ja/"; keep /jp.
Web Strategy & Optimization Lead 1 hour
Fix the English alternate
hreflang en points to "/" not "/?r=0".
Web Strategy & Optimization Lead 1 hour
Resubmit
Japanese sitemap and URL inspection in Search Console.
Web Strategy & Optimization Lead 1 day
Finish the homepage
Translate the English H1 on /ja.
Localization team 2 days
Route demos
Japanese demo form to the Japan Sales Director.
Marketing Operations 1 week
Brief partners
Japanese case study links for SI partners.
Partner Sales Manager, Japan 1 week
Track
Impressions, clicks and demos from /ja weekly.
Senior Marketing Analyst weekly
Why it works
Remove the /ja and /ja/ lines from robots.txt (keep /jp, which only redirects), resubmit the sitemap in Search Console, and watch Japanese impressions. At the same time point the English homepage alternate at "/" instead of "/?r=0" (also blocked), translate the English H1 left on /ja, and add a Japanese demo form that routes to the Japan sales team.
The pages, translations and hreflang already exist, so the cost is one file edit. Japanese buyers research in Japanese, and the new sellers and partners get inbound demand and local proof to send instead of starting cold.
Ready to use
ChecklistJapanese site launch check
[ ] Remove "Disallow: /ja" and "Disallow: /ja/" from robots.txt [ ] Keep /jp (redirect only) [ ] English hreflang on the homepage points to / [ ] Resubmit sitemap.xml in Search Console [ ] Translate the English H1 on /ja [ ] Japanese demo form routed to the Japan team [ ] Weekly report: /ja impressions, clicks, demos
Risks and how to handle them
Some Japanese pages are thin or partly English
Unblock first, then noindex the weakest pages instead of the whole folder.
A sudden jump in indexed pages
Watch crawl stats; the sitemap and canonicals are already in place.
Evidence
- Your websiterobots.txt (checked October 21, 2026) contains "Disallow: /ja" and "Disallow: /ja/" (and /jp), yet the sitemap lists 1,681 Japanese URLs (784 connector pages, 290 /people pages, 195 activation pages, 34 case studies), each with a self-referencing canonical and hreflang, and every page's language switcher offers Japanese. /jp redirects to the Japanese resource library.Source
- HiringJapan: a Sales Director (remote, Japan) "responsible for building out our enterprise customer base within various regions in Japan" who will "Organize POC implementations of dbt Cloud Enterprise", and a Partner Sales Manager "based in and around Tokyo" for "Technology, SI, and GSI partners in the region". Both posted August 7, 2026 and still open in October.Source
- Your websiteThe homepage's English hreflang alternate is "/?r=0", a URL that robots.txt's "Disallow: /?" also blocks, while the canonical is "/". The Japanese homepage /ja still shows an English first H1, "Connect your AI to your data", above the Japanese one.Source
- HiringWeb Strategy & Optimization Lead (posted October 6, 2026 in New York, Austin and Philadelphia; also Oakland and Denver): "Define the long-term web growth strategy across Fivetran.com, getdbt.com, and other high-impact web experiences"; "experimentation roadmaps across critical user journeys, including the Homepage, Navigation, Pricing, Signup"; tools named are Webflow, Sanity, Optimizely, GA4, Amplitude, Looker and Microsoft Clarity; and "Identify emerging opportunities in AI, personalization".Source