iTownPage company data extraction is useful when a team has reviewed itp.ne.jp detail-page URLs and needs a clean CSV export for research, newsrooms, SEO briefs, sales-list QA, or monitoring. The iTown Page Details Scraper template turns that URL list into status-aware rows.
Problem
Why iTownPage sales lists break in spreadsheets
iTownPage is the itp.ne.jp business and facility search service from NTT Town Page. A research team usually needs something narrower: one row per selected business, a source URL that can be audited, and enough contact fields to decide the next step.
Manual collection is fine for five pages. It breaks when a team needs 50, 500, or a repeating watchlist. People copy the wrong phone number, mix old and new rows, and lose the original detail-page URL before the data reaches a CRM, spreadsheet, or editorial notebook.
A sales list is only useful when every row can be traced back to the exact source page, run date, visible fields, and validation decision.
Before automation, review the current iTownPage overview and terms of use. For contractual rights or redistribution, compare this workflow with NTT Town Page's marketing database and iTown DB Search.
Personas
Who uses an iTownPage business details scraper?
| Persona | Pain | CSV outcome |
|---|---|---|
| Market researchers | Local category mapping gets stuck in browser tabs and notes. | Export company names, phone numbers, homepage links, source URLs, and status fields for segmentation. |
| Newsrooms | Business claims need source pages an editor can recheck. | Preserve iTownPage URLs, contact fields, homepage references, and blocked-page markers beside story notes. |
| SEO teams | Local entity briefs need accurate business names, homepage domains, and location-specific source material. | Build structured rows for category audits, citation checks, and content planning. |
| Sales operations | Lead lists need contact fields but also QA before outreach. | Filter blanks, duplicates, Access Denied rows, and no-detail pages before CRM import. |
| Monitoring teams | Rechecking the same businesses by hand creates inconsistent snapshots. | Re-run a fixed URL list and compare status, homepage, phone, and visible detail changes over time. |
Searches like how to build iTownPage sales lists, scrape iTownPage detail pages, and best iTownPage scraper for leads point to the same gap: useful browser pages need to become a repeatable file.
Workflow
How the template delivers iTownPage company data extraction
The bundled JSON workflow is compact: Set Window Size -> Navigate -> Wait for Page Load -> Sleep -> Wait for Element -> Structured Export -> Loop Continue. Navigate holds a multi-URL input list. Structured Export reads from the page body, writes headers, and appends every result into the same CSV.
Status logic matters as much as contact fields. During template analysis, some itp.ne.jp pages returned Access Denied. The workflow checks for that text, avoids phone-like digits from blocked URLs, and writes No_detail_page when a page is blocked, missing, or too low-signal to trust.
| Workflow part | What it controls | Why teams care |
|---|---|---|
| Navigate | The reviewed iTownPage detail URLs | Keeps scope explicit and repeatable. |
| Wait blocks | Page load timing and body visibility | Reduces false blanks from slow pages. |
| Structured Export | CSV filename, append mode, and columns | Produces rows a spreadsheet or CRM import queue can inspect. |
| JavaScript fallbacks | Headings, metadata, mailto links, tel links, and page text | Keeps extraction resilient when one selector changes. |
| Loop Continue | Multi-URL progression | Processes a controlled list without manual copy-paste. |
Output
What the iTownPage to CSV export contains
There is no bundled CSV sample, so the JSON definition is the authoritative sample of the workflow. Your first small run creates the file you should validate.
Itown-page-details-cloud-only.csvColumn
会社名
Company or shop name from headings, metadata, or title fallback.
Column
メールアドレス
Email from mailto links or visible page text when present.
Column
URL
Current iTownPage URL after navigation.
Column
電話番号
Phone from tel links or labeled text, disabled on Access Denied pages.
Column
ホームページ
External business homepage after excluding common map, social, and itp.ne.jp links.
Column
オリジナル_URL
Original or current URL retained for reconciliation.
Column
No_detail_page
Blank for likely valid pages; Access Denied or No detail page for failed rows.
| Field group | How to use it | QA rule |
|---|---|---|
| Identity | Match business names to reviewed source URLs. | Dedupe by source URL before matching by company name. |
| Contact | Review phone, email, and homepage before outreach. | Treat blanks as unknown, not proof that contact details do not exist. |
| Status | Separate successful rows from blocked or missing pages. | Filter No_detail_page before analysis or CRM import. |
Use cases
Concrete Japan business directory scraping workflows
Build a local supplier shortlist
Collect candidate URLs for a region and category, export contact fields, then group rows by homepage presence, phone availability, and status.
Prepare a newsroom evidence sheet
Preserve source URLs, homepage links, and status values beside editorial notes so an editor can reopen the exact page behind each row.
Create SEO entity briefs
Compare names, homepage domains, and directory source URLs while planning local landing pages, citation cleanup, or competitor research.
Clean a lead list before outreach
Filter Access Denied and No detail page rows, remove duplicate source URLs, and verify phone or homepage fields before any CRM upload.
Monitor a fixed watchlist
Re-run the same detail URLs monthly and compare homepage, phone, email, and status changes without rebuilding the spreadsheet by hand.
The best iTownPage scraper for leads is not always the one that touches the most pages. For research teams, the better workflow is controlled, reviewable, and honest about failed rows.
Validation
How to validate iTownPage sales lists
For a serious list, start with 5 to 10 URLs. Keep the browser visible, open the CSV after the run, and check the first rows against the live pages. Record the run date, URL source, export filename, usable rows, status rows, and selector edits.
| Symptom | Likely cause | Action |
|---|---|---|
Every row says Access Denied | The source returned an access-control page. | Stop and review policy, pace, and whether this project should use a licensed route. |
| Company names are blank | The URL is not a detail page or the layout changed. | Open the URL manually before editing selectors. |
| Phone values look wrong | Blocked-page text or unrelated digits were matched. | Keep the blocked-page guard enabled and validate against the browser. |
| The CSV has duplicates | Append mode reused an old file or the URL list repeats. | Rename the file per run and dedupe by オリジナル_URL. |
| Homepage is blank | The page may not expose an external site. | Treat it as unknown and verify high-value rows manually. |
For implementation steps, use the companion iTownPage scraping tutorial. For tool selection, read the iTownPage scraper alternatives comparison or browse the template library.
FAQ
iTownPage sales list FAQ
Use it when researchers, newsrooms, SEO teams, sales operations, or monitoring teams have reviewed detail-page URLs and need a CSV with company name, phone, email, homepage, source URL, and status.
Next step
Download the iTown Page Details Scraper
Use the iTown Page Details Scraper template when your team has a reviewed URL list, a clear research purpose, and a need for local CSV output. Run a small validation batch first, then decide whether the local desktop workflow, a hosted scraper, or an official licensed data route is the right long-term fit.