Skip to content

Use "of" instead of "for" with URL (EK00049)

One phrasing for every link reference keeps documentation uniform. Use "URL of" rather than "URL for" when describing the resource a link points to.

Using “URL of” rather than “URL for” gives you one phrasing for every reference to a link, which keeps documentation uniform. EkLine flags the phrase “URL for” when it describes a resource and suggests “URL of” instead (rule EK00049).

Why say “URL of” instead of “URL for”?

Section titled “Why say “URL of” instead of “URL for”?”

Small wording choices add up. When some pages say “the URL for the page” and others say “the URL of the page,” readers notice the inconsistency, and it makes the documentation feel unedited. Settling on “URL of” gives you one phrasing for every reference to a link, which reads more naturally and keeps your content uniform.

EK00049 matches the phrase “URL for” when it describes a resource and suggests “URL of”.

  • Incorrect: Copy the URL for the resource.
  • Correct: Copy the URL of the resource.
  • Incorrect: Share the URLs for these pages with your team.
  • Correct: Share the URLs of these pages with your team.

Replace “URL for” with “URL of” when you describe the link that points to a resource.

Use “URL of” when you describe the link that points to a resource — “the URL of the page”. This keeps every reference to a link consistent.

When “for” expresses purpose rather than a reference, such as “a URL for testing”, the sentence may be correct. Review the suggestion in context before you apply it.

PropertyValue
Rule IDEK00049
CategoryConsistency
Default severitySuggestion
Enabled by defaultYes

To keep “URL for” on one line, add an inline comment with a reason:

<!-- ekline-ignore-next-line EK00049 -- "for" expresses purpose here -->
Generate a URL for testing.

To disable the rule across your project, add it to the ignore list in your configuration file.

  • EK00040 — Use standardized word-list terms
  • EK00042 — Prefer concise words over complex terms