Track every directory submission as a record with evidence, not as a hopeful backlink. Your tracker should show where you submitted, what happened, whether a public listing is currently live, the publisher-assigned link attribute, who can access the listing, and when to check again.
Create one record for each directory
Use one row, card, or dashboard record per directory. A useful tracker includes the directory name, submission URL, submission date, status, approval URL, domain rating, link type, UTM source, and notes. The approval URL is evidence that a listing is live, while UTM parameters help identify referral traffic separately in your analytics tool. SubmitSaaS’s tracking guide distinguishes these two jobs.
Do not count a submitted form as a published listing. Publishers decide whether to approve a submission and which link attribute to assign. Ranks notes that one daily submission does not guarantee one live backlink per day.
| Field | What to record | Why it matters |
|---|---|---|
| Directory | Directory name and submission URL | Lets teammates locate the source and submission route. |
| Submission date | Date the form was sent | Drives a repeatable follow-up schedule. |
| Status | Pending, Approved, Rejected, or Stale | Keeps submissions separate from live listings. |
| Live URL | Public URL that resolves | Provides evidence of a current listing. |
| Link attribute | Observed publisher-assigned attribute | Separates link classification from approval status. |
| Access | Login or managed-email access method | Supports edits where the directory permits them. |
| Next follow-up | Date plus next check | Keeps unresolved entries visible. |
Use statuses that mean one thing
Give each status an observable meaning. Approval is a publisher decision you have observed. A live URL is evidence that a public page currently resolves. Record both when possible instead of assuming that one observation proves the other.
Keep link attribute in its own field, not in the status. An approved listing can carry a publisher-assigned dofollow, nofollow, UGC, or sponsored attribute, and that classification does not alter the approval outcome.
- Pending: submitted, with no observed approval or rejection.
- Approved: publisher approval has been observed and listing evidence is recorded.
- Rejected: a publisher rejection has been observed.
- Stale: the follow-up window passed without a recorded resolution. It is unresolved, not rejected.
- Live-listing audit: confirm the public URL resolves, verify the expected link attribute, and review whether the description is current.
Schedule follow-ups instead of relying on memory
Set the next follow-up when you create the record. The example schedule below comes from SubmitSaaS's tracking guide, not a deadline publishers have agreed to meet. Follow a directory's stated review window when it differs.
A quarterly audit helps detect silent changes that no notification has reported. Open the recorded live URL, verify that it resolves, inspect the observed link attribute, and compare the description with current positioning. Record the observation date to distinguish current evidence from an earlier result. Adjust the audit cadence based on the listing’s value and your team’s available time.
- Day 0: create the record, mark it Pending, and schedule the day-7 check.
- Around day 7: check the submission inbox or confirmation message and log what you observe.
- Around day 14: check for approval or rejection. Add a live URL only when a public listing resolves.
- Around day 30: use an appropriate follow-up route if the directory provides one.
- Around day 60: mark unresolved records Stale while retaining submission history.
- Quarterly: independently audit live listings and timestamp the observation.
Keep access details useful and controlled
Directories handle account access differently. Record whether a listing uses a login, a managed email-link workflow, or another access method. Keep sensitive credentials in your approved secure system rather than a broadly shared spreadsheet. Also note whether editing is available for that particular listing.
Ranks records saved directory listing credentials when possible. Some directories use managed email links instead of passwords, and editability depends on the directory. An access-method field is therefore more accurate than assuming every listing has a reusable username and password.
- Record the account email or access owner so approval messages can be located later.
- Link to the secure credential location instead of placing passwords in an open tracker.
- Note the actual edit route once you have observed it.
- After updating a listing, record the description-review date and schedule another live audit.
Centralize submission tracking in Ranks
For teams that want this record beside ongoing SEO work, Ranks centralizes submission history, publisher, domain rating, approval status, and publisher-assigned attributes including dofollow, nofollow, UGC, and sponsored. It handles submissions and account creation where needed, then tracks submissions through publication checks.
Treat the dashboard as the operating record. Inspect approval status before reporting a result, use a live listing as public evidence, and check the recorded link attribute after publication. For valuable listings, assign a manual next-review date to a person or task system.
Each paid project receives one article and one available backlink submission per day, according to Ranks. The available-submission qualifier matters: neither daily activity nor a paid plan guarantees publisher approval. Check the current plan limits on the product site rather than using a tracking guide as a price list.
Turn your tracker into a weekly decision tool
For a weekly review, sort unresolved records by next follow-up date. The example below is hypothetical: it illustrates how evidence changes the next action, not a directory's promised turnaround.
| Observation | Record update | Next action |
|---|---|---|
| A confirmation email arrived, but no public listing can be found. | Keep Pending; retain the receipt. | Check after the publisher's stated review window. |
| An approval email arrived and the public page contains the correct product link. | Record approval, the live URL, observed link attribute and check date. | Schedule a later accuracy check; do not submit again. |
| The team's follow-up window passed with no decision. | Mark Stale, not Rejected. | Use the publisher's permitted follow-up route or retain as unresolved. |



