London Gazette Strike Off Notices Scraper

Search and monitor London Gazette strike off notices without an account or API key. The Actor finds official Gazette issue pages in a publication window, reads their cited PDFs, classifies the strike-off stage, and exports company names and registration numbers with complete retrieval provenance.

Each dataset item represents one Gazette page, not one company. A page can cite dozens of companies, exposed in companyReferences and counted in companyCount.

What can this London Gazette strike-off monitor do?

• Search a date window for pages containing statutory strike-off language.
• Keep only proposed, final, retraction, or other strike-off pages.
• Filter cited text by a company name or registration number.
• Parse a known Gazette issue or supplement page directly.
• Export the complete PDF text alongside normalized fields.
• Preserve canonical page, PDF, search, issue, page, and retrieval references.
• Deduplicate pages by their stable Gazette URL.

The Actor currently limits discovery results to the London edition. Explicit URLs may point to London, Edinburgh, or Belfast issue pages.

Who is this Actor for?

• Company-formation and registry platforms checking Gazette events.
• Credit-risk and supplier-monitoring teams.
• Accountants, insolvency specialists, and compliance analysts.
• Researchers building dated UK corporate-event datasets.
• Automation teams scheduling a daily run and comparing dataset rows.

This is a focused retrieval product. It does not submit DS01 forms, modify Companies House records, or send legal notices.

Why use structured Gazette notice records?

The Gazette search result is a page-level public record, while the page PDF contains the complete statutory wording and company list. The Actor combines those official surfaces into one auditable row. You receive both normalized fields for filtering and the original cited content for verification.

No residential proxy, browser, login, or Companies House API key is required.

What data is extracted?

Field	Meaning
noticeId	Stable edition-issue-page identity
noticeType	proposed-strike-off, final-strike-off, retraction, or other-strike-off
edition	Gazette edition from the URL
issueNumber	Official issue number
pageNumber	Issue or supplement page number
publicationDate	Gazette publication date (YYYY-MM-DD)
title	Search result or issue-page title
companyReferences	Parsed company names and registration numbers
companyCount	Number of unique parsed registration numbers
citedContent	Full text extracted from the official PDF page
canonicalUrl	Public Gazette issue-page URL
pdfUrl	Official PDF used for extraction
searchUrl	Discovery query URL, or null for explicit URLs
source	The Gazette
retrievedAt	UTC retrieval timestamp

How to search recent strike-off notices

1. Choose a startDate and endDate.
2. Optionally select one or more noticeTypes.
3. Optionally enter a company name or number in searchText.
4. Set maxItems to the maximum number of Gazette pages you need.
5. Run the Actor and open the default dataset.
6. Schedule the same input daily for incremental monitoring.

Example:

{
  "startDate": "2026-09-01",
  "endDate": "2026-09-14",
  "noticeTypes": ["proposed-strike-off"],
  "maxItems": 10
}

How to extract a specific Gazette page

Provide noticeUrls when you already know the official issue-page URL:

{
  "noticeUrls": [
    "https://www.thegazette.co.uk/London/issue/901095/supplement/4923"
  ],
  "startDate": "2026-09-01",
  "endDate": "2026-09-14",
  "maxItems": 1
}

Discovery search is skipped, but date, type, and text filters still apply. Non-Gazette hosts and unsupported URL shapes fail closed.

Input parameters

Input	Type	Default	Description
startDate	string	Seven days ago	Earliest publication date
endDate	string	Today	Latest publication date
searchText	string	—	Case-insensitive filter over title and cited PDF text
noticeTypes	string[]	All	Normalized stages to keep
noticeUrls	string[]	—	Specific Gazette issue pages; disables discovery
maxItems	integer	20	Maximum accepted page records, from 1 to 500

Dates must use YYYY-MM-DD, and startDate cannot be later than endDate.

Output example

A real page produces the following shape (content shortened here):

{
  "noticeId": "London-901095-4923",
  "noticeType": "proposed-strike-off",
  "edition": "London",
  "issueNumber": "901095",
  "pageNumber": "4923",
  "publicationDate": "2026-09-08",
  "title": "The London Gazette, Supplement 901095, Page 4923",
  "companyReferences": [
    { "companyName": "S AND S FAMILY PARTNERSHIP LLP", "companyNumber": "OC430521" }
  ],
  "companyCount": 37,
  "citedContent": "COMPANIES ACT 2006 ...",
  "canonicalUrl": "https://www.thegazette.co.uk/London/issue/901095/supplement/4923",
  "pdfUrl": "https://www.thegazette.co.uk/London/issue/901095/supplement/4923/data.pdf",
  "searchUrl": null,
  "source": "The Gazette",
  "retrievedAt": "2026-09-14T06:30:00.000Z"
}

Use the full citedContent and official links when a decision requires source verification.

How much does it cost to monitor London Gazette strike-off notices?

Pay-per-event billing has a one-time $0.005 start event plus one item event per accepted Gazette page. The current BRONZE item price is $0.0076 per page; higher account tiers receive the tier curve shown by Apify at run time.

At the current BRONZE price:

• 1 notice page costs about $0.0126 including start.
• 10 notice pages cost about $0.081 including start.
• 100 notice pages cost about $0.765 including start.

A page may include many companies; embedded company references have no separate charge. Failed, duplicate, filtered, or non-strike-off pages do not emit an item event.

Daily monitoring workflow

Use an Apify Schedule with a rolling date window:

1. Run shortly after Gazette publication.
2. Set the window wide enough to overlap the previous run.
3. Use noticeId or canonicalUrl as the deduplication key downstream.
4. Compare the current dataset with your saved notice IDs.
5. Review noticeType, companyReferences, and citedContent for new events.

The Actor exports records; it does not itself send alerts or maintain a cross-run state database.

Spreadsheet and data-pipeline exports

Apify datasets can be downloaded as JSON, CSV, Excel, XML, or RSS. Arrays such as companyReferences are richest in JSON. For a flat spreadsheet, keep the notice-level row and expand the company array in your ETL tool.

Useful integration patterns include:

• Load page records into a compliance warehouse.
• Expand companyReferences into a company-event bridge table.
• Join companyNumber to an authorized Companies House workflow.
• Trigger review when a watched company number appears.
• Preserve canonicalUrl, pdfUrl, and retrievedAt in audit logs.

Run through the Apify API with cURL

curl -X POST \
  "https://api.apify.com/v2/acts/automation-lab~uk-gazette-strike-off-notices-monitor/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"startDate":"2026-09-01","endDate":"2026-09-14","maxItems":3}'

To wait for output directly, use the synchronous dataset-items endpoint supported by the Apify API.

JavaScript API example

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/uk-gazette-strike-off-notices-monitor').call({
  startDate: '2026-09-01',
  endDate: '2026-09-14',
  noticeTypes: ['final-strike-off'],
  maxItems: 20,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python API example

from apify_client import ApifyClient
import os

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('automation-lab/uk-gazette-strike-off-notices-monitor').call(run_input={
    'startDate': '2026-09-01',
    'endDate': '2026-09-14',
    'maxItems': 20,
})
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

Use with MCP and AI assistants

Add the Apify MCP server to Claude Code:

claude mcp add --transport http apify \
  "https://mcp.apify.com?tools=automation-lab/uk-gazette-strike-off-notices-monitor"

Claude Desktop setup

Use this configuration in Claude Desktop:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=automation-lab/uk-gazette-strike-off-notices-monitor"
    }
  }
}

Cursor setup

Add the same apify server URL in Cursor Settings → MCP.

VS Code setup

Add the same HTTP MCP server to your VS Code MCP configuration and start it from the MCP servers panel.

Example prompts:

• “Find London Gazette strike-off pages published between 1 and 14 September 2026.”
• “Parse this Gazette supplement page and list its company numbers.”
• “Return only final strike-off pages and summarize the cited statutory wording.”

Always verify consequential conclusions against the returned source links.

Reliability, retries, and failure behavior

Requests have a 30-second timeout and up to three bounded attempts for transient failures. Deterministic client errors are not retried blindly. One malformed page is logged and skipped so other discovered pages can complete.

The run fails for invalid date ranges, unsupported explicit URLs, or unrecoverable discovery errors. An explicit page without strike-off wording is rejected rather than emitted under a misleading type.

Coverage and limitations

• Discovery currently emits London edition pages only.
• Explicit URLs can target London, Edinburgh, or Belfast pages.
• One dataset item is a Gazette page, which can contain many statutory sections.
• Company references are parsed from PDF text layout; inspect citedContent when companyCount is unexpectedly low.
• The Gazette can correct, replace, or retract notices after initial publication.
• This Actor monitors public records; it does not determine current legal company status.
• It does not file DS01 forms or query private Companies House services.

Responsible and legal use

The Actor reads publicly accessible official Gazette pages and PDFs. Follow The Gazette's terms, Apify's policies, applicable database rights, privacy law, and your organization's retention rules. Do not treat automated output as legal advice or as a substitute for the current official record.

Keep provenance fields when redistributing results. Minimize personal-data processing when a page contains names or addresses that are not needed for your purpose.

Troubleshooting

Why did my run return no rows?

The date window may contain no matching London pages, or your noticeTypes/searchText filter may exclude them. Broaden the window and remove optional filters before diagnosing a source failure.

Why is companyCount lower than expected?

Some PDFs use unusual layouts or continue a list across pages. Read citedContent, follow neighboring issue pages, and use the official PDF link for verification.

Why was my explicit URL rejected?

Use a public thegazette.co.uk/{Edition}/issue/{number}/page/{number} or /supplement/{number} URL. Search pages, PDFs, and third-party links are not accepted as canonical notice-page input.

FAQ

Does this include every Companies House filing?
No. It targets Gazette pages with strike-off wording, not the complete Companies House filing stream.

Does maxItems limit companies?
No. It limits accepted Gazette page records. Each row can carry many company references.

Can I monitor one company?
Yes. Put its exact company name or registration number in searchText, or provide a known issue-page URL.

Can I schedule it daily?
Yes. Use an Apify Schedule and deduplicate downstream by noticeId.

Is a successful match proof that a company is currently dissolved?
No. Notice wording and stage matter, and later notices or registry updates can supersede it.

Related automation-lab Actors

This Actor is intentionally standalone because the portfolio does not currently contain another automation-lab Actor for the same Gazette notice workflow. Combine its company numbers with your own authorized registry, risk, notification, or warehouse integrations.