SCRECS.C. Code 40-57-135Read at the source
Real estate advertising rules in South Carolina
When advertising property owned by another, in any medium including signage, the licensee must clearly identify the FULL name of the brokerage firm they are associated with.
What has to be on the post
- the licensed name of your brokerage
The part that is easy to get wrong
South Carolina accepts a link to the brokerage homepage for online advertising, but the rule asks for the full name, not an abbreviation. In force since 21 May 2025.
The numbers, in one place
| 1 | requirement SCREC puts on the ad itself |
|---|---|
| 51 | US jurisdictions LOKAL carries, read at the source |
| 15 | of them set a text SIZE rule, not just a mention |
| 2 | require the licence number on the advertisement |
| no ratio | South Carolina fixes no size ratio between the two |
| 2026 | the year this rule was last read at the source |
| 29 % | of US jurisdictions turn this into a measurable size rule |
| 14,853 | US markets LOKAL can pre-fill, down to the ZIP code |
| $29 | a month for the tool that checks this before you post |
A worked example, and why one template cannot do it
Two states contradict each other outright, and it is the clearest case study of why this matters. Texas asks for the broker name at 50 % of the largest agent contact text; Illinois asks for 100 %. A layout built for Texas is therefore non-compliant in Illinois, and the difference is not a missing word but a font size. That result is only visible if something measures the pixels after drawing them, which is what LOKAL does before you post.
Where this comes from
SCREC, S.C. Code 40-57-135. Read the rule at the source
Your state regulator is not the only one with a say. These federal sources apply on top of S.C. Code 40-57-135, and no state commission will remind you of them:
- HUD, fair housing advertising and marketing
- FTC endorsement guides, for posts that carry a claim
- CFPB, when a post mentions rates or financing
LOKAL reproduces published regulator guidance and checks what it draws against it. It is not legal advice, and it does not replace your broker's review.
LOKAL checks this on the image, not on a form.
Pick your market, set your signature once, and LOKAL measures what it actually drew against S.C. Code 40-57-135 before you post. It carries all 51 US jurisdictions.
Open the generator for South CarolinaOther jurisdictions
Questions
- What must appear on a real estate ad in South Carolina?
- Under S.C. Code 40-57-135, SCREC requires the licensed name of your brokerage. When advertising property owned by another, in any medium including signage, the licensee must clearly identify the FULL name of the brokerage firm they are associated with.
- Does a social media post count as advertising in South Carolina?
- SCREC writes its rule for advertising in any medium, and a market-update post that invites contact is advertising. The safest place for the disclosures is inside the image itself, because a caption can be truncated and a bio can be missed.
- Is there a size requirement in South Carolina?
- South Carolina sets no size or prominence ratio between the brokerage name and your own. The mention has to be there and be readable; how big it is relative to your name is not fixed by S.C. Code 40-57-135.
- Anything easy to get wrong in South Carolina?
- South Carolina accepts a link to the brokerage homepage for online advertising, but the rule asks for the full name, not an abbreviation. In force since 21 May 2025.
How this page is written and checked
Written by the engineering team at INEYA Studio, the software studio that builds LOKAL. The South Carolina rule on this page was read at SCREC's own published text in 2026, not summarised from a third party.
It is checked automatically on every build against the compliance table the product itself applies: S.C. Code 40-57-135 appears on this page only because LOKAL enforces exactly that rule when it draws your image. A page that claimed a requirement the product does not check would fail the build.
Reviewed by the engineering team at INEYA Studio on 2026-09-17, and re-checked automatically on every deployment. Found something out of date? Tell us and we will correct it.