Real Estate Listing Page Checks With Claude Code: Move-In Costs, Photos, and Viewing CTAs

A real estate listing page can look attractive and still lose the visitor right above the viewing button. The photos are clean, the rent is visible, but the move-in costs, guarantor-company fee, insurance, availability status, and update date sit far below the CTA. The 30-minute fix is to put costs, photo checks, availability, and update dates in one review table before the viewing form.

Primary references for the Japanese version include the Real Estate Fair Trade Council page on fair competition rules, the Tokyo-area council note on when advertising may start, its rental-specific examples on campaign rent and rental display, the rental listing display table Appendix 9, and MLIT’s interpretation document for the Real Estate Brokerage Act PDF. This article is not legal advice. It shows a Claude Code workflow for surfacing issues before a human approves publication.

For CSV and stale-page operations, see real estate listing CSV updates. This article narrows the work to what the visitor sees before requesting a viewing: photos, move-in costs, status, update dates, and the CTA.

Key Takeaways

• Show rent, management fee, deposit, key money, guarantor-company cost, insurance, and other move-in costs before the viewing CTA.
• Ask Claude Code to compare page copy, CSV rows, photo filenames, form fields, and update dates.
• Humans keep availability status, transaction terms, advertising display, cost accuracy, photo rights, viewing slots, and publish approval.
• Track viewing request rate, form reach rate, cost-question count, publication rollback count, and minutes spent on corrections.
• The first action is to add a cost-and-update table above one existing viewing button.

Where Listing Pages Break

Property visitors usually scan a phone screen in a strict order: photos, rent, station distance, floor plan, costs, then viewing. If the page shows only the headline rent near the CTA, visitors have to guess the rest. They may wonder whether the guarantor company is required, whether insurance is separate, whether key exchange or cleaning fees exist, and whether the listing was updated recently.

The more serious risk is stale availability. A rented room, an old rent value, previous-room photos, or a viewing button left active while status is still unconfirmed can make the page feel like bait. MLIT’s interpretation document discusses bait advertising and false advertising under the broad area of exaggerated advertising. Claude Code should not write louder copy here. It should stop the page when evidence is missing.

Appendix 9 from the fair-trade rules lists items for used rental apartments and similar listings, including rent, key-money-type payments, deposits and guarantees, insurance, guarantor-company conditions, management fees, move-in timing, transaction-condition validity, publication or latest update date, and next scheduled update. Those items become the practical review checklist.

Workflow: Review Photos, Costs, And The Viewing CTA Together

A listing review should not read only the page body. Put the listing CSV, photo folder, viewing form, status memo, update date, and page draft in one table. The table follows the visitor’s screen order, not the office’s data-entry order.

Visitor area	Information to show	Human review
Photos	exterior, room, kitchen, bath, storage, neighborhood	wrong room and photo rights
Cost area	rent, management fee, deposit, key money, guarantor, insurance, other fees	cost accuracy
Availability	open, applied, pending confirmation, move-in timing	bait-ad risk
Viewing CTA	candidate times, reply timing, documents, when to call	form drop-off
Footer or nearby note	update date, next update, transaction type, license number	display requirements

Once this table exists, the prompt becomes specific. Instead of asking Claude Code to improve the page, ask it to cross-check photos, move-in costs, viewing CTA, update dates, and availability against the source data. The branch manager or licensed reviewer then approves only the rows that are true.

Claude Code Scope And Human Scope

Claude Code can inventory headings, compare CSV fields, check photo counts and filenames, find missing cost labels, inspect CTA placement, locate update dates, and flag risky phrases. It can put station distance, building age, rent, guarantor-company note, insurance, move-in timing, and status into a table.

Humans decide availability, transaction terms, cost wording, advertising compliance, photo-use rights, portal rules, viewing slot operation, and publication. If Claude Code says the page is ready, that still means nothing until the person responsible checks whether the room is still available, whether the figures match the owner-approved terms, and whether publication timing is allowed.

Do not pass owner names, tenant names, applicant data, phone numbers, exact room notes, or internal negotiation memos to the model. The model needs listing ID, public costs, photo filenames, status, URL, update dates, and form labels. Mask internal data before using receptionist notes or sales memos.

3 Use Cases

Use case 1: Find missing move-in costs before the CTA

• Input: listing page copy, rental CSV, cost sheet, guarantor condition, insurance note, viewing form.
• Output: a table separating rent, management fee, deposit, key money, guarantor, insurance, other fees, and needs-review rows.
• Human review: owner-approved terms, media rules, cost wording, and publish approval.

Use case 2: Stop wrong-room photos

• Input: photo filenames, listing ID, draft page, floor plan, amenity list, previous photo set.
• Output: photo category, missing photo, likely wrong listing, and needs-caption rows.
• Human review: photo rights, room number, current condition, renovation timing, and publishable range.

Use case 3: Put viewing CTA and update dates in one screen

• Input: viewing form, availability memo, latest update date, next scheduled update date, move-in timing, listing status.
• Output: four CTA-adjacent lines, confirmation email draft, call-first conditions, and update-date check.
• Human review: availability, viewing slots, reply timing, phone routing, advertising display, and publish timing.

Copy-Paste Prompt

あなたは不動産会社の物件ページ公開前レビュー担当です。
広告文を盛らず、写真、初期費用、内見CTA、更新日、取引条件の抜けを表にしてください。

入力:
- 物件ページ本文
- 物件CSVの該当行
- 写真一覧
- 初期費用の内訳
- 内見予約フォーム
- 更新日と次回更新予定日

確認してほしいこと:
1. 賃料、管理費、敷金、礼金、保証会社、保険、その他費用が分かれているか
2. 写真が外観、室内、キッチン、水回り、収納、周辺のどれを示すか分かるか
3. 内見CTAの上に、空き状況、候補日時、返信目安、必要な持ち物があるか
4. 更新日、次回更新予定日、入居可能時期、取引態様が見えるか
5. 「すぐ決まります」「最安」「絶対」など根拠のない強い表現がないか
6. 人が確認する項目を、広告表示、取引条件、費用、写真権利、公開承認に分ける
7. 今日30分で直す1箇所を1つだけ出す

制約:
- 存在しない設備や費用を作らない
- 成約済み、募集停止、確認中の物件を公開可にしない
- 法律判断は断定せず「要確認」と書く

Working Check Code

This Node.js sample does not connect to a real website. It checks whether a listing object has the core cost, photo, update-date, and viewing-CTA fields before publication.

const listing = {
  title: "駅徒歩7分 1LDK",
  rent: 92000,
  managementFee: 8000,
  deposit: "1か月",
  keyMoney: "1か月",
  guarantorFee: "",
  insurance: "要確認",
  updatedAt: "2026-07-19",
  nextUpdateAt: "2026-07-26",
  photos: ["exterior.jpg", "living.jpg", "kitchen.jpg"],
  cta: "内見予約",
  status: "published",
};

const required = [
  ["rent", "賃料"],
  ["managementFee", "管理費・共益費"],
  ["deposit", "敷金・保証金"],
  ["keyMoney", "礼金"],
  ["guarantorFee", "家賃保証会社の条件と額"],
  ["insurance", "損害保険料等"],
  ["updatedAt", "直前の更新日"],
  ["nextUpdateAt", "次回の更新予定日"],
  ["cta", "内見CTA"],
];

const missing = required
  .filter(([key]) => listing[key] === undefined || listing[key] === "")
  .map(([, label]) => label);

const photoWarnings = listing.photos.length < 4
  ? ["写真が4枚未満です。外観、室内、キッチン、水回りを確認してください。"]
  : [];

const ctaWarnings = /内見|見学|問い合わせ/.test(listing.cta)
  ? []
  : ["CTAが内見や問い合わせにつながっていません。"];

const warnings = [...missing, ...photoWarnings, ...ctaWarnings];

console.log({
  canPublish: warnings.length === 0 && listing.status === "published",
  warnings,
});

Run it with node check-listing.mjs. In production, connect the same idea to your listing CSV, CMS draft, and photo-folder export. If warnings is not empty, the page goes back to review.

Pitfall: Common Failure Patterns

Pitfall	Cause	Fix
Rent is visible but costs are hidden	CTA design centered only on rent	Move a cost table above the CTA
Rented listing remains public	CSV update and page publish are separate	Stop when status is not published
Photos belong to another room	Photo filenames are not checked against listing ID	Compare photo name, date, and listing ID
Strong ad copy appears	The model was asked to make the page persuasive	Tell it to use facts only and flag unsupported claims
Update date is tiny	The date was treated as footer housekeeping	Put latest and next update near the CTA

FAQ

Q. Should every move-in cost be shown? A. A human reviewer decides by property type and media rule. For user trust, costs that affect the viewing decision should not be hidden below the CTA.

Q. Can Claude Code decide advertising compliance? A. No. It can flag missing evidence, risky claims, stale dates, and empty fields. Humans make the decision.

Q. How many photos are enough? A. Count alone is weak. Check whether exterior, room, kitchen, bath, storage, and neighborhood information are covered.

Q. How is this different from the CSV update article? A. The CSV article covers operational status and URL maintenance. This article covers the visitor’s page before requesting a viewing.

What I Verified

For this article I checked the slug, frontmatter, internal link, external sources, CTA, code block, and final section. The sample code flags an empty guarantor-company fee, too few photos, and missing CTA wording. The next practical action is to open one live listing page and place move-in cost, latest update, next update, and availability above the viewing button. For team rollout, bring CSV columns, public URLs, photo-folder rules, and the viewing form to training and consultation.