Calculate TF divided by CF
TF/CF = majesticTF / majesticCF. A domain with TF 12 and CF 24 has a ratio of 0.50. TF 18 and CF 30 gives 0.60. These are illustrative calculations, not results for any particular domain.
DomDetailer's API returns TF and CF separately; the ratio is derived by the web tools or your own integration. It is not another independent measurement. Store the two original fields so someone reviewing an export can understand how the ratio was produced.
Use the same lookup scope and comparable dates. A ratio built from a domain-level TF and a page-level CF would describe mismatched inputs.
Handle zero and missing values
When CF is zero, division is undefined. Show a blank, an em dash or a named unavailable value; do not turn it into a reassuring ratio of 1. A missing score is also different from a returned numeric zero.
When CF is positive and TF is zero, the arithmetic ratio is zero. Preserve that fact while investigating whether the provider has limited evidence. An API error should remain an error row, rather than becoming an all-zero domain profile.
For an exported sheet with TF in B2 and CF in C2, an illustrative formula is =IF(OR(B2="",C2="",C2=0),"",B2/C2). Use your spreadsheet's local argument separator where required, and make sure the input columns contain numeric scores.
Why a high ratio is not a pass mark
TF 2 and CF 2 produces 1.00. TF 25 and CF 40 produces 0.625. Sorting by ratio alone puts the tiny profile first even though it has much less evidence behind the scores. Review score size as well as balance.
Similarly, a lower ratio may identify a candidate worth checking for repeated or low-value links, but it cannot name the cause. Majestic recommends assessing the broader profile before concluding that a TF/CF difference is a problem.
A numerical rule can help manage workload if you treat it as your own screening policy. Document why you chose it, review a sample of rejected candidates and revisit it for different topics. Avoid describing that policy as a provider-approved quality threshold.
Use the ratio to choose what to inspect
- Fetch TF and CF for unique domains in the bulk metrics checker.
- Keep error and unknown rows separate from numeric results.
- Sort or filter to identify unusual combinations, then check referring domains and topical relevance.
- Inspect anchors and source URLs using the bulk backlink checker.
- Record your evidence and decision alongside the metrics.
If you automate this process, the domain metrics API returns the two original numbers in one successful request costing one credit.
Questions
Is a TF/CF ratio of 0.5 always good?
No universal threshold establishes domain quality. Look at the absolute scores, topic, referring domains and current links before making a decision.
Can the TF/CF ratio exceed 1?
Yes. If TF is higher than a positive CF, the quotient exceeds 1. That arithmetic result does not guarantee useful links or rankings.