Vérifier une page immobilière avec Claude Code: frais, photos et CTA de visite

Une page immobilière peut perdre une demande même avec de belles photos. Le loyer est visible, mais le dépôt, la garantie, l’assurance, la disponibilité et la date de mise à jour sont loin du bouton de visite. L’action de 30 minutes consiste à placer une table de frais, photos, statut et dates juste avant le formulaire.

Cet article ne remplace pas une revue juridique. Claude Code lit la page, la ligne CSV, les noms de photos, le formulaire et les dates, puis sort les points à vérifier. La personne garde les conditions, la publicité, les droits photo, la disponibilité et l’approbation.

Les références principales sont les règles japonaises de concurrence loyale immobilière, les exemples de location, les tableaux d’informations requises et le document MLIT sur la loi immobilière.: RFTC, rental examples, required display table, MLIT PDF. For CSV operations, see real estate CSV workflow.

Points clés

• Put total move-in cost near the viewing CTA, not only at the bottom.
• Compare page copy, CSV row, photo names, form fields, status, and update dates before publishing.
• Claude Code should extract missing items and risky claims; humans keep final approval.
• Track viewing request rate, form reach rate, cost questions, correction count, and review time.
• The first action is one listing page, one CTA area, one cost-and-update table.

Où la page se casse

The reader sees photos first, then rent, station distance, floor plan, cost, and the viewing button. If the page only shows the headline rent near the CTA, the reader must guess guarantor-company cost, insurance, key exchange, cleaning, update date, and availability. That uncertainty is enough to move to another listing. The business impact is not abstract: fewer viewing requests, more cost questions, more apologies when a stale room is still online.

Stale availability is the scarier failure. A rented room stays public, old rent remains on one page, previous-room photos are reused, or the viewing form accepts requests before status is confirmed. Claude Code should not make the copy more exciting. It should compare the page against source data and stop rows that need human review.

Workflow: photos, frais et CTA ensemble

Review the listing in the visitor’s screen order. Put page draft, listing CSV, photo folder, viewing form, status memo, update date, and next update date into one table. This makes small errors visible before they become public.

Area	Check	Human review
Photos	exterior, room, kitchen, bath, storage, area	rights and wrong room
Costs	rent, management, deposit, key money, guarantor, insurance, other fees	approved terms
Status	available, applied, pending, move-in timing	publication allowed
CTA	viewing dates, reply time, documents, when to call	operation and staffing
Dates	latest update, next update, transaction type	display review

The table changes the prompt. Instead of asking for better marketing copy, ask Claude Code to cross-check each artifact. The result is a review sheet a manager can approve or reject.

Ce que Claude Code fait et ce que l’humain décide

Claude Code can inventory headings, compare CSV fields, inspect photo filenames, find missing cost labels, locate update dates, count CTA buttons, and flag words such as absolute claims or unsupported comparisons. It can output a table with blank, mismatched, and needs-review rows.

The human reviewer decides availability, transaction terms, advertising wording, cost figures, photo rights, portal rules, viewing-slot operation, and publication. Owner names, tenant names, applicant data, phone numbers, and internal negotiation memos should not be sent to the model. Public listing ID, costs, status, URL, photo names, and form labels are enough.

3 cas d’usage

Use case 1: Move-in cost check

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

Use case 2: Photo mismatch check

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

Use case 3: CTA and update-date check

• Input: viewing form, availability memo, latest update, next update, move-in timing, status.
• Output: four CTA-adjacent lines, confirmation email draft, call-first conditions, date checks.
• Human review: availability, viewing slots, reply time, call routing, publish timing.

Prompt à copier

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

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

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

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

Code de vérification

This Node.js sample checks a small listing object. It has no network access and does not decide legal compliance. It only returns warnings 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,
});

Pitfall: erreurs fréquentes

Failure	Cause	Fix
Costs hidden below CTA	rent-centered design	move cost table above CTA
Stale listing public	status and publish split	block non-published status
Wrong photos	filenames not checked	compare photo name, date, ID
Unsupported ad copy	model asked to persuade	facts only, flag claims
Update date hidden	treated as footer text	place update near CTA

Questions fréquentes

Q. Can the model approve the ad? A. No. It can flag missing fields, stale dates, risky claims, and mismatched photos. A person approves publication.

Q. What number should we watch? A. Watch viewing request rate, form reach rate, cost-question count, correction count, and review time. These numbers sit closer to revenue than page views alone.

Q. What is the first task? A. Pick one published listing and place move-in cost, latest update, next update, and status above the viewing CTA.

Ce que j’ai vérifié

I checked slug, frontmatter, external links, internal link, CTA, code block, and final section for this article. The sample code reports missing guarantor fee and too few photos, then points the listing back to review. For a team workflow, bring CSV columns, public URLs, photo rules, and the viewing form to formation et conseil.