Skip to content

why-moved: 페이지 렌더가 색인 정책을 index 로 되돌리던 것 (#33 후속) #35

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mossland merged 1 commit into from
Aug 20, 2026
Merged

why-moved: 페이지 렌더가 색인 정책을 index 로 되돌리던 것 (#33 후속) #35

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion app/asset/[symbol]/why-moved/[date]/page.tsx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -102,13 +102,19 @@ export default async function WhyMovedPage({ params }: Props) {

const assetLabel = entity?.label || symbol.toUpperCase();

// The policy is the gate's, not a constant — and it must be passed
// explicitly here. registerSeoPage() defaults to 'index', so rendering a
// quiet-day article (a crawler fetching it is enough) silently promoted the
// row back to index and undid scripts/reindex-why-moved.ts.
const indexPolicy = whyMovedIndexPolicy(article.pulses);
registerSeoPage({
path: `/asset/${canonicalSymbol}/why-moved/${date}`,
page_type: "event",
canonical_id: `${canonicalSymbol}-${date}`,
title: article.title,
meta_description: article.oneLine.slice(0, 200),
quality_score: 0.85,
index_policy: indexPolicy,
quality_score: indexPolicy === "index" ? 0.85 : 0.3,
lastmod: article.generatedAt,
});

Expand Down
Loading