A directory submission tracker records a business listing from initial research through publication and review. Its most important job is to stop a submitted form being counted as a live backlink. Separate the application status, public listing URL, website-link evidence and actual business outcomes.
Download the free directory submission tracker CSV. The file contains a header and one illustrative example row, not approved publishers or completed submissions. Import it into Excel or Google Sheets, replace the example and follow the workflow below. More worksheets are available in the resources hub and templates library.
What the tracker should answer
A teammate should be able to open a record and understand why the directory was chosen, whether the business is eligible, what was submitted, which costs apply and what happens next. If a public page exists, they should be able to open it and verify the destination.
A spreadsheet full of domain names and “done” labels cannot answer those questions. It can conceal duplicate applications, unexpected renewals and profiles that never became public. Useful tracking keeps enough evidence to make a decision without becoming an account database.
Start with the fields you will actually maintain. Add analytics fields when placements become live, and keep a separate evidence source where detailed screenshots or correspondence need to be retained.
The downloadable columns
| Field group | Columns | Why they matter |
|---|---|---|
| Identity | Prospect ID, Site Name, Category, Submit URL | Find the original route and avoid duplicate records |
| Qualification | Eligibility Evidence, Audience Fit, Checked Date | Explain why the route is suitable today |
| Costs | Required Fee, Currency, Renewal Date | Separate free routes from ongoing obligations |
| Work | Owner, Status, Submitted Date, Next Action, Next Review | Keep pending work accountable |
| Publication | Listing URL, Target URL, Link Status, Link Attributes, Link Checked Date | Separate a public listing from a checked link |
| Evidence | Evidence URL, Notes | Retain source references and unresolved questions |
Use dates consistently, such as 2026-09-30. A checked date means the team inspected a particular fact then. It does not mean the publisher guarantees the information stays unchanged.
Keep currency separate from amount so campaign totals do not silently mix pounds, dollars and euros. If conversion is needed, document the exchange-rate source and date outside the basic tracker rather than guessing.
Define one record per intended listing
A practical record represents one business or product on one publisher's intended listing route. If a company has multiple genuinely separate products and the platform permits separate profiles, give each its own record. If it is the same profile with a correction request, keep the original ID.
Normalize names and URLs enough to find duplicates. Two submission links on the same domain may lead to the same profile process. Check before creating a second application. Preserve the original submitted destination so later redirects do not erase campaign history.
Do not use a new row for every follow-up message. Add the follow-up date and next action to the existing record or maintain a separate activity log keyed to the prospect ID. This keeps application counts meaningful.
Use a small, explicit status list
Recommended application statuses are “Needs research,” “Eligible,” “Ready,” “Submitted,” “Published,” “Rejected” and “Paused.” These are workflow suggestions, not publisher-provided states. Document what each means for your team.
| Status | Definition | Evidence required |
|---|---|---|
| Needs research | Candidate found but not qualified | Publisher and route |
| Eligible | Current rules match the business | Official rules and fit notes |
| Ready | Facts, assets and terms reviewed | Approved pack and destination |
| Submitted | Application sent | Date and confirmation reference |
| Published | Public profile available | Listing URL checked while logged out |
| Rejected | Route or application declined | Reason and evidence |
| Paused | Specific question or dependency unresolved | Next action and owner |
A listing can be published while its link status is “Not checked” or “Not found.” Keep the two fields independent. This prevents the team from treating all public profiles as verified backlinks.
Record link checks separately
Use link states such as “Not checked,” “Found,” “Not found in fetched HTML” and “Manual review needed.” The wording matters because a server tool can be blocked or unable to inspect JavaScript-rendered content.
After publication, check the exact source and intended target with the live backlink checker. Save the final destination and observed attributes. If the tool cannot retrieve the source, inspect the browser view and record what you can actually establish.
Do not add “Google indexed” merely because a page loads. The backlink indexing guide explains the difference between live, crawlable, indexed and reported. Most businesses cannot inspect another publisher's Search Console property.
Qualification before submission
Use the eligibility and audience fields as gates. Save the official rules, proposed category and an explanation of why a customer would use it. If the directory sells guaranteed ranking credit or the business must invent facts to qualify, reject the route.
The directory listing quality guide supplies worked decisions. The prospect qualification checklist is useful when the opportunity is an editorial pitch rather than a structured listing.
Do not use “high DR” as the complete fit note. A useful note identifies the category, audience and destination. Recorded metrics can be supporting data, but they do not establish customer relevance or eligibility.
Worked example: from prospect to public listing
This example is fictional and demonstrates status changes only. A team researching software directories creates record D-014 for a project management product. It saves the official submission route, category and eligibility page, with the date checked.
After reviewing the rules, it marks the record “Eligible.” The team then prepares approved text and screenshots using the listing preparation guide. It checks the destination page and moves the record to “Ready.”
On submission day, it stores the receipt reference and changes the status to “Submitted.” It does not fill in a public listing URL unless one actually exists. The next review date is based on the publisher's stated process rather than an invented universal waiting period.
When the profile becomes public, the team records its URL and marks the application “Published.” It checks the website button, notes nofollow if that is what the page contains, and records “Found” with the check date. It has a verified observed placement, not proof of search indexing or future traffic.
Worked example: a paid option with unclear terms
Imagine another candidate with a useful audience but an unclear premium subscription. The researcher saves the pricing page and records “Paused: renewal terms unresolved.” The owner contacts the publisher through the official route.
If the fee is recurring, the owner adds the amount, currency and renewal date before approval. If the platform only sells a review service without promising publication, the notes state that distinction. If the terms cannot be clarified, the team can reject the route without losing the research history.
Keep the database purchase cost separate from publisher fees. The Complete Backlink Database Bundle supplies a research CSV; it does not pay directory charges or guarantee approvals. The database guide explains that deliverable.
Useful spreadsheet views
Create a “Ready to submit” view filtered to Ready and assigned to an owner. Create a “Needs follow-up” view filtered to Submitted with a next-review date due. Create a “Verify publication” view for Published records whose link status is not Found.
A “Renewals” view can show paid records with an upcoming renewal date. A “Rejected routes” view helps prevent repeated research. These views are more useful than sorting every row by domain metric and working through the file indiscriminately.
Keep the underlying data intact when creating views. Do not delete pending or rejected records simply to make a dashboard appear successful. Those records explain time spent and campaign decisions.
Counts that avoid misleading reports
Count unique prospect IDs when reporting applications. Count unique public listing URLs when reporting published profiles. Count records with a completed link check separately, and state whether the count represents pages or referring domains.
For an application-to-publication rate, divide published records by submitted applications from the same cohort. Exclude unsubmitted candidates and explain how pending applications are treated. Do not divide by the entire research database and call it an acceptance rate.
For a link-check completion rate, divide published records with completed checks by all published records due for checking. This measures operational completeness, not ranking value. Use referral measurement for traffic and sales outcomes.
Dates and follow-up hygiene
Use Next Review for an actionable date, not a promise of publication. If the publisher says review normally takes a certain time, record its statement and source. A research file's approval estimate should be checked against the current publisher process.
Avoid repeated duplicate applications as a follow-up strategy. Use the platform's support or status route. If the business has already been listed, check whether the appropriate action is claiming or correcting the existing profile.
Set a future maintenance date for important listings. Changes in business details, product names or website URLs can make an old profile misleading. A tracker should remain useful after the first campaign batch ends.
Keep evidence useful and private information limited
Save public rules and listing URLs in the tracker. For confirmations, store a reference to your team's controlled records rather than pasting private account links into a broadly shared sheet. Do not add passwords, card numbers or access tokens.
Only include contact data when it is needed for the workflow, and restrict access appropriately. An example address in the downloadable file is not a real contact to message. Replace illustrative data with your own approved campaign information.
Treat exported CSVs carefully when importing untrusted third-party text into a spreadsheet. Review cells before enabling external connections or executing anything embedded. The supplied worksheet uses ordinary illustrative text and does not require scripts, macros or integrations.
What to read next
Prepare the listing description and asset pack, maintain a prospecting spreadsheet, and compare research database fields. Use the directory submission plan for capacity and budgeting, then backlink indexing checks for reporting questions.