When a SaaS directory rejects your submission, read its notice and current requirements before trying again. Correct a specific mistake if the publisher permits an update or reconsideration. If your product genuinely does not meet its eligibility criteria, stop pursuing that listing and choose a better-fit directory. If the reason is unclear, ask one focused question rather than submitting the same listing again.
Confirm the outcome before changing your listing
Find the publisher’s email, account message or submission page, and save the exact wording of the decision. An unanswered submission is not necessarily a rejection. Ranks shows where it submitted a product and distinguishes listings awaiting approval from live listings, but publishers control approval; use the submission record for context, not as a substitute for the publisher’s explanation.
Compare the notice with the directory’s current submission instructions and category criteria. Check what you actually sent—not just the product page you have today. A wrong URL, incomplete description or unsupported category claim calls for a different response from a product that does not qualify. For example, Gartner Peer Insights says vendors should review its active markets for the best match, and that it notifies vendors when a product falls below a market definition’s minimum criteria. It retains discretion over whether a product fits a market. Those are Peer Insights rules, not a universal policy for SaaS directories.
Correct a fixable error; move on from a real mismatch
Make the decision using the reason given, the requirement it refers to and evidence from your actual product. If a submitted fact is wrong, prepare the corrected field and supporting product page, then check the publisher’s instructions for an edit or reconsideration route. Do not create a duplicate submission merely because you can fix the copy. If the requirement accurately excludes your product, a better description will not make it eligible. Look for a genuinely suitable category or another directory instead; do not relabel the product to evade the rule.
Here is a fictional worked decision. A founder submitted the same SaaS product to two directories. Directory A’s notice identifies the product URL as invalid: the submission used https://old.example, while the founder’s current, working product page is https://app.example. The founder checks Directory A’s instructions, corrects the URL through its permitted route and asks whether the corrected submission can be reviewed. That is a retry worth making, not a promise of approval. Directory B says the product does not qualify for the selected category. The founder compares the category’s current criteria with the product’s actual features, confirms the missing requirement and stops pursuing that category. If another category is available, the founder checks its criteria afresh rather than assuming eligibility.
This is about an application that has not become an approved listing. If a public listing is already live but its details became outdated after a name or website change, use the separate guide to updating SaaS directory listings after a rebrand.
Ask one precise question when the reason is unclear
If the notice says only “not approved,” check the publisher’s current contact instructions before writing. Keep your message short: identify the submission, quote or paraphrase the notice accurately, name the requirement you checked and ask what specific issue—if any—can be corrected. Ask whether an update is permitted; do not assume the publisher offers an appeal or another attempt.
You can adapt this inquiry: “Hello, I submitted [product name] for [directory or category] on [date] using [submitted product URL]. The notice says [exact reason or ‘not approved’]. I checked [relevant current requirement] and believe [one factual explanation]. Could you clarify which requirement the submission did not meet, and whether a correction is permitted? Thank you.” Attach evidence only if it directly answers that question, and wait for the publisher’s response before treating a possible retry as an approved path.
Keep the result accurate and choose your next target
Keep the original submission date, notice, requirement checked, correction or inquiry sent, and publisher response together. Distinguish “awaiting reply” from “rejected,” and never mark a corrected submission live until you can open its public listing. Ranks provides submission-history and status context for submissions it handles, including awaiting and live listings; the publisher still decides whether a listing goes live. For a fuller record-keeping workflow, see the guide to tracking SaaS directory submissions.
Once a publisher confirms the mismatch or declines a correction, put your effort into an eligible opportunity rather than repeated requests to the same directory. The guide to prioritizing SaaS directories covers choosing the next target; the decision here is whether this rejected submission has a factual, permitted fix.
