# NAKAMOTO Daily Operations: Trading Academy, Investing, Personal Finance, and Bitcoin

This is the single working checklist for improving the four priority sectors: Trading Academy, Investing, Personal Finance, and Bitcoin.

Primary objective: grow from hundreds of visitors to 1,000,000+ unique visitors through organic, sustainable growth.

Daily publishing target: publish up to 100 source-checked items when enough real, useful, non-repeated source material exists. Do not invent stories, fake freshness, repeat old headlines without new evidence, or add low-quality filler just to hit a number.

## Core Daily Operations Focus

Use this as the default scope when the owner says `NAKAMOTO Daily Operations`, `Execute daily operation`, `Nakamoto Daily Growth Operation now`, `Execute full section operation and Google Microsoft growth review`, or `Execute daily section operation`.

## Saved Daily Execution Command

When the owner says `today lists`, `execute all`, `execute everything`, `daily execution`, `daily task from lists`, or `do it all`, use this saved checklist as the default daily scope. Do not leave the daily package half-finished.

1. Add fresh source-checked news when real current material exists.
2. Update `crypto-news-today.html`.
3. Create the dated `news-YYYY-MM-DD.html` archive.
4. Update `bitcoin-blog.html`.
5. Create the dated `bitcoin-blog-YYYY-MM-DD.html` archive.
6. Create `today-source-pack-YYYY-MM-DD.html`.
7. Update Trading Academy.
8. Update Investing and Finance routes.
9. Update Personal Finance and Money Library routes.
10. Update Bitcoin and beginner routes.
11. Check the main desks: Bitcoin, ETF, Economy, Finance, Security, Stablecoins, RWA, and Policy.
12. Update the homepage Today routes.
13. Update the news archive.
14. Update `daily-operations.html`.
15. Create the dated `daily-operations-YYYY-MM-DD.html` archive.
16. Update search entries in `script.js`.
17. Update `feed.xml`.
18. Update `sitemap.xml`.
19. Check for unwanted advertising code and the known removed marker patterns before publishing.
20. Test local pages, dated-page links, JavaScript, sitemap XML, and feed XML.
21. Sync to GitLab when the owner asks for sync or says execute everything.
22. Check the live Netlify site after deploy.
23. Preserve older pages and useful history; update and link instead of deleting.
24. Leave unrelated user changes alone, especially files already modified or deleted before the operation.
25. Report what changed, what passed verification, what was synced, and anything intentionally left untouched.

This saved command is the daily execution memory. It applies every day unless the owner explicitly says not to sync, not to publish, or to handle only one section.

## Whole Section Daily Operation Rule

From June 30, 2026 onward, the daily operation means update the whole website section system, not only News and Blog. The daily job is to check every major section, improve what is useful, and avoid filler. If a section has no real fresh news, improve its internal links, source routes, metadata, readability, examples, checklists, or reader path instead.

Main rule:

1. Update the four priority hubs first.
2. Update News, Blog, source pack, homepage, archive, RSS, sitemap, search, indexing queue, and dashboards second.
3. Check the wider section system third.
4. Do not invent news, fake freshness, repeat old headlines without a real new development, or add low-quality filler.
5. Record what changed before verification.
6. Sync only when requested or when the command includes sync.

Whole section system to check during daily operations:

1. News.
2. Blog.
3. Research.
4. Research Foundation.
5. Data & Analytics.
6. Statistics.
7. Risk Management.
8. Research Methods.
9. Tools & Calculators.
10. Guides & Tutorials.
11. Corporate Finance.
12. Capital Markets.
13. Economy / Macroeconomics.
14. Policy / Regulation.
15. Tax & Accounting.
16. Space / Technology.
17. AI / Technology.
18. Cybersecurity.
19. Entrepreneurship.
20. Business.
21. Wealth Building.
22. Financial Literacy.
23. Real Estate.
24. Financial Institutions.
25. Careers & Education.
26. Psychology / Decision Making.
27. Productivity.
28. Global Affairs / Geopolitics.
29. Stablecoins.
30. RWA / Tokenization.
31. Markets.
32. Sources / References.
33. Premium.
34. Daily Brief.
35. Newsletter.
36. Search.
37. Resources.
38. Archives.
39. Dashboards.
40. Indexing Queue.

Daily check for each section:

1. Check if it needs fresh content.
2. Check if it has stale dates.
3. Check if it has weak text.
4. Check if it has missing internal links.
5. Check if it has missing source links.
6. Check if it has weak metadata.
7. Check if it has poor readability.
8. Check if it has mobile layout issues.
9. Check if it has dark/light mode issues.
10. Check if it has broken links.
11. Improve one useful thing when needed.
12. Add one reader route when useful.
13. Add one read-next link when useful.
14. Add one source route when useful.
15. Add one checklist or example when useful.
16. Keep education and risk disclaimers where needed.
17. Avoid unsupported advice.
18. Avoid clickbait.
19. Avoid filler.
20. Record what changed.

Daily growth and SEO checks:

1. Improve homepage discovery.
2. Improve category discovery.
3. Improve internal linking.
4. Improve article recommendations.
5. Improve newsletter routes.
6. Improve return-tomorrow routes.
7. Improve source trust.
8. Improve Google and Microsoft indexing queue.
9. Improve pages with impressions but low CTR when Search Console data is available.
10. Improve pages ranking near positions 8 to 20 when Search Console data is available.
11. Improve underperforming landing pages when analytics data is available.
12. Improve high-potential evergreen pages.
13. Improve related article paths.
14. Improve reader session flow.
15. Check titles, descriptions, canonicals, Open Graph, Twitter cards, schema, sitemap, RSS, robots, internal links, duplicate pages, orphan pages, and crawlability.

Daily verification:

1. Check changed pages for broken text.
2. Check stale today blocks.
3. Check JavaScript syntax.
4. Check sitemap XML.
5. Check RSS XML.
6. Check links on important new pages.
7. Check no temporary files are committed.
8. Review changed files.
9. Commit clean changes.
10. Sync to GitLab when requested or when the operation includes sync.

## Four Priority Hub Rule

Every daily section operation must touch the four priority hubs as one connected system:

1. Trading Academy: risk, process, journal, drills, and no-signal education.
2. Investing: portfolio policy, ETF/product structure, market research, and source checks.
3. Personal Finance / Money Library: budget, saving, debt, emergency fund, and readiness before risk.
4. Bitcoin / Bitcoin Origin: beginner clarity, custody, source verification, ETF context, and security.

For each hub, add or improve one useful reader path and at least one relevant internal link to another priority hub when it improves the journey.

## Daily Section Operation Command

Primary command:

`Execute daily section operation`

Use this command when the owner wants the full daily task without immediate deployment.

Deploy command:

`Execute daily section operation and sync`

Use this command when the owner wants the full daily task, local verification, Git commit, and GitLab sync.

No-sync command:

`Execute daily section operation, do not sync`

Use this command when the owner wants the work prepared locally and reviewed before deployment.

Full daily coverage:

1. Trading Academy
2. Investing
3. Bitcoin / Bitcoin Origin
4. Personal Finance / Money Library
5. News
6. Blog
7. Homepage
8. Daily section dashboards
9. Section update archives
10. Internal linking map
11. Source tracker
12. Article recommendation blocks
13. SEO metadata
14. Sitemap and RSS feed
15. Google/Microsoft indexing queue
16. Search discovery coverage
17. Local verification
18. GitLab sync only when requested or when the command includes `and sync`

Daily output requirements:

1. Add or improve fresh daily content for News.
2. Add or improve fresh daily content for Blog.
3. Add or improve fresh daily content for Investing.
4. Add or improve fresh daily content for Personal Finance.
5. Add or improve fresh daily content for Bitcoin / Bitcoin Origin.
6. Add or improve fresh daily content for Trading Academy.
7. Update the daily operation archive.
8. Update the homepage route to today's best work.
9. Update section dashboards and section archives.
10. Update sitemap, feed, posted log, and indexing queue after material changes.
11. Check that new and important existing pages are discoverable through sitemap, search, internal links, and relevant hub routes.

## Daily Publisher Revenue Add-On

Run this after content quality checks. The goal is legitimate revenue through better reader value, not fake clicks or policy-risk tactics.

1. Update or verify `most-read-today.html` with the strongest useful routes, using real analytics when available and editorial curation when data is unavailable.
2. Add at least one relevant internal link from the homepage, news desk, blog, or priority hub into a deeper article, guide, source pack, checklist, calculator, or series.
3. Check that sponsor placements are labelled `Advertisement` or `Sponsored` and are not placed near buttons, forms, navigation controls, or download-style UI that could cause accidental clicks.
4. Check that ad density stays modest: one early reading-break slot, one mid-page slot on long pages, and one footer sponsor area by default.
5. Check GA4/Microsoft events when available: `reader_scroll_depth`, `reader_engaged_time`, `revenue_module_view`, and `recommended_route_click`.
6. Improve one newsletter capture route with a clear reason to return.
7. Improve one article series path so readers can continue naturally without clickbait.
8. Review mobile readability before sync: no squeezed ad slots, no hidden text, no overlapping controls, no forced interstitials.
9. Keep affiliate and sponsored links marked with `nofollow sponsored noopener noreferrer` where relevant.
10. If any ad network serves adult, misleading, malware-style, forced redirect, fake wallet, fake broker, or fake download creatives, pause that network before syncing.

## Daily Learning Asset Operation

Run this after the four priority hubs are updated. These assets make the site deeper, more useful, and easier to explore.

1. Mini courses: improve one lesson, task, or internal link in the 7-day money reset, Bitcoin safety, or business validation course.
2. Country guides: improve one country route or official-source checklist for UK, USA, Canada, or Australia.
3. Calculators: test and improve one practical calculator: break-even, savings rate, mortgage pressure, compound growth, emergency fund, debt payoff, or rental yield.
4. Comparison hub: add or improve one honest comparison that helps readers choose between paths without hype.
5. Glossary: add or improve plain-English terms that support Trading Academy, Investing, Personal Finance, Bitcoin, or business education.
6. Beginner hub: keep the first learning path clear, calm, and linked to the next best course.
7. Templates and worksheets: connect practical pages to a worksheet, checklist, or calculator when useful.
8. Growth dashboard: review Google Search Console, GA4, Google Trends, PageSpeed/Lighthouse, Bing Webmaster Tools, Microsoft Clarity, and Microsoft Ads/UET only when real data is available.
9. Newsletter capture: add or improve a relevant signup route where the reader has a real reason to return.
10. Visual/layout quality: check mobile and desktop spacing, typography, card density, icons, theme toggle, and dark/light contrast before sync.

Priority support pages:

1. `mini-courses.html`
2. `7-day-money-reset.html`
3. `7-day-bitcoin-safety.html`
4. `7-day-business-validation.html`
5. `country-guides.html`
6. `uk-money-tax-guide.html`
7. `usa-money-tax-guide.html`
8. `canada-money-tax-guide.html`
9. `australia-money-tax-guide.html`
10. `growth-dashboard.html`
11. `planning-calculators.html`
12. `comparison-hub.html`
13. `business-finance-glossary.html`

## Daily Traffic Rally Section Operation

These sections are now part of the permanent traffic-growth framework. Use them during daily operations when there is real, useful, source-checkable material. Do not force fake updates.

Daily repeat-visit sections:

1. `daily-market-brief.html`
2. `economic-calendar.html`
3. `crypto-regulation-tracker.html`
4. `personal-finance-daily.html`
5. `real-estate-mortgage-watch.html`
6. `beginner-explainers.html`
7. `scam-safety-alerts.html`
8. `newsletter-daily-brief.html`

Platform and safety sections:

1. `broker-platform-education.html`
2. `exchange-education.html`
3. `funded-trading-education.html`
4. `cybersecurity.html`
5. `stablecoins.html`
6. `ai-finance.html`
7. `space-technology.html`

Markets and macro sections:

1. `interest-rates.html`
2. `inflation.html`
3. `central-banks.html`
4. `bonds-yields.html`
5. `stocks-etfs.html`
6. `commodities.html`
7. `gold-bitcoin.html`
8. `forex-currencies.html`

Income, business, and institution sections:

1. `income-growth.html`
2. `side-hustles.html`
3. `freelancing.html`
4. `small-business-guides.html`
5. `banks.html`
6. `brokerages.html`
7. `asset-managers.html`
8. `payment-companies.html`
9. `insurance.html`
10. `pension-funds.html`
11. `official-data-hub.html`
12. `monthly-wealth-plan.html`

Daily traffic rules:

1. Update the daily market brief only with verified, useful market context.
2. Update the economic calendar only around meaningful macro events.
3. Link news into at least one evergreen hub when it helps the reader.
4. Improve one beginner explainer, calculator, comparison, or glossary route each day.
5. Improve one trust/source route each day: official data, source pack, or source tracker.
6. Improve one retention route each day: newsletter, mini-course, monthly plan, or weekly review.
7. Keep every page education-first. Avoid spam, clickbait, fake urgency, or unsupported financial claims.

## Daily Click, Impression, and CTR Growth Operation

Run this after the content update and before sync. The goal is to turn existing impressions into more clicks, and turn strong pages into more search visibility without clickbait.

1. Find pages that already receive impressions or are likely to receive impressions: homepage, live news, dated news archive, Bitcoin blog, Trading Academy, Investing, Money Library, Bitcoin start page, source pack, and indexing queue.
2. Improve one title or meta description when the current search result is too generic, unclear, or not matched to search intent.
3. Add one above-the-fold route from the homepage or daily operations page to the strongest current page.
4. Add internal links from today's news into the four priority hubs: Trading Academy, Investing, Personal Finance, and Bitcoin.
5. Add internal links from evergreen hubs back to the freshest daily update when the connection is genuinely useful.
6. Check that every updated page has a clear first action: read news, verify sources, open guide, run checklist, or return tomorrow.
7. Add a question-style heading, FAQ, checklist, or comparison block only when it answers a real reader question.
8. Keep titles useful and honest. Do not use fake urgency, price promises, exaggerated claims, or clickbait.
9. Add updated pages to the Google and Microsoft indexing queue only after meaningful changes.
10. Record the click/impression action in the dated daily operation archive before syncing.
11. Run a discovery audit: HTML pages should be in the sitemap unless intentionally excluded, and site search should surface archive/deep pages through the sitemap fallback.

Fastest wins:

1. High impressions + low CTR: rewrite title and description.
2. Good content + weak internal links: add read-next routes.
3. Fresh daily story + no evergreen path: link to the right guide.
4. Strong evergreen guide + no current route: link it from today's brief.
5. Good page + poor first screen: improve the first paragraph and primary CTA.

## Tomorrow Upgrade Queue

Use this queue during the next daily operation after the fresh news and section updates are complete. These upgrades are quality upgrades, not filler.

Tomorrow daily command:

`Execute daily operation`

Tomorrow focus:

1. Add fresh daily news only when source-checked.
2. Update the Bitcoin blog with the main market thesis.
3. Upgrade Trading Academy with one new drill or checklist.
4. Upgrade Investing with one product, ETF, or portfolio explainer.
5. Upgrade Personal Finance with one money checklist or guide.
6. Add internal links between all updated pages.
7. Update homepage Today First routes.
8. Update source tracker.
9. Update sitemap, feed, and indexing queue.
10. Verify locally, then sync only when the owner says `sync`.

Tomorrow extra 10 upgrade ideas:

1. Bitcoin options expiry recap.
2. ETF flow explainer.
3. Portfolio risk checklist.
4. Trading journal prompt.
5. Money emergency-fund example.
6. Search page improvement.
7. Better article recommendation blocks.
8. News archive cleanup.
9. Source pack improvement.
10. Homepage headline polish.

## Reader Growth System

Use this system after the daily section update when the owner says to add everything, improve retention, or grow returning visitors.

1. Keep the reader dashboard visible from homepage, login, register, search, and article save strips.
2. Keep saved-article buttons active on useful content pages.
3. Keep topic preferences focused on Trading Academy, Investing, Personal Finance, Bitcoin, News, and Safety.
4. Add newsletter capture to high-intent pages: homepage, dashboard, daily brief, contact, and strong article pages.
5. Track newsletter submissions with GA4, Microsoft UET, and Clarity-friendly events when the scripts are available.
6. Track reader account navigation, save clicks, preference saves, and saved-article clears.
7. Use preferences to personalize homepage return routes when browser storage is available.
8. Add the dashboard, register page, daily brief, and best-of route to search discovery.
9. Keep recommendation blocks relevant to page topic, not random recency.
10. Do not claim real protected login exists until a secure auth provider or backend is connected.

Reader system next build queue:

1. Connect real authentication provider.
2. Sync saved articles across devices.
3. Add email verification.
4. Add unsubscribe preference center.
5. Add reader topic alerts.
6. Add weekly digest preferences.
7. Add reading history.
8. Add continue-reading position.
9. Add beginner/advanced preference.
10. Add Google and Microsoft event dashboards for newsletter, save, search, and dashboard actions.

## Tax And Accounting Expansion Queue

Use this queue when the owner says to work on tax, accounting, country tax pages, crypto tax, trading accounting, investor records, or tomorrow's tax section.

Execution rules:

1. Treat all tax/accounting content as education only, not personal tax advice.
2. Start every country page with official tax authority sources.
3. Add a clear disclaimer, last-updated date, and "ask a qualified professional" note.
4. Do not guess rules that depend on residency, personal circumstances, timing, entity type, or product structure.
5. Link tax pages back to Trading Academy, Investing, Personal Finance, and Bitcoin only where useful.
6. Prioritize records, checklists, official-source links, and reader questions before complex tax conclusions.
7. Avoid affiliate placement on tax pages unless the page is a clear software comparison with disclosure.
8. Update the sitemap and search page after publishing tax/accounting pages.

First 10 tax/accounting pages:

1. Tax & Accounting hub: `tax-accounting.html`.
2. UK Crypto Tax Guide: `uk-crypto-tax-guide.html`.
3. USA Digital Assets Tax Guide: `usa-digital-assets-tax-guide.html`.
4. Crypto Tax Checklist: `crypto-tax-checklist.html`.
5. Trading Record Keeping Guide: `trading-record-keeping-guide.html`.
6. Capital Gains Tax Basics: `capital-gains-tax-basics.html`.
7. Crypto Losses Guide.
8. Tax Document Checklist.
9. Accountant Question Checklist.
10. Tax Deadline Calendar.

Official source starter list:

1. UK: HMRC Cryptoassets Manual.
2. USA: IRS Digital Assets.
3. Canada: CRA Cryptocurrency Guide.
4. Australia: ATO Crypto Asset Investments.

Daily tax/accounting operation:

1. Pick one country or one universal record-keeping topic.
2. Read official sources first.
3. Build one page with disclaimer, source links, record checklist, reader questions, and next steps.
4. Add internal links to the four priority sectors.
5. Verify links and metadata.
6. Add to sitemap, search, and daily operation archive.

## Daily Marketing Execution Layer

Use this layer during daily operations after content quality, source checks, and section updates are complete. Marketing work must support the four priority sectors and must not weaken trust.

Execution source:

1. `MARKETING_ENGINE_100.md` is the internal execution backlog. Use the ideas to improve real pages, sections, search visibility, email capture, trust, and content quality.
2. `marketing-growth-operation.html` remains the public daily marketing checklist and asset route.
3. Do not publish marketing-strategy pages as standalone site content unless the owner explicitly asks. Use strategy files to execute improvements.

Marketing priorities:

1. Grow organic search traffic through better content quality, topic depth, internal links, metadata, and crawlable archives.
2. Grow returning visitors through daily brief routes, weekly reports, section dashboards, return paths, and clear read-next flows.
3. Grow engagement through better article recommendations, search discovery, source packs, tools, checklists, and beginner paths.
4. Grow trust through source tracker updates, editorial policy links, correction routes, disclaimers, official source links, and risk labels.
5. Grow conversions through newsletter CTAs, daily brief placement, tool CTAs, contact routes, and high-intent guide paths.
6. Use only Google and Microsoft products for analytics, webmaster, trends, Promotion, behavior analysis, and performance checks.
7. Record the marketing action, affected page, reason, and next metric whenever a meaningful marketing change is made.

Daily marketing checklist:

1. Core growth: update the homepage route, keep priority sections fresh, add internal links, improve content discovery, and preserve archives.
2. SEO: improve titles, descriptions, headings, canonical URLs, structured data, sitemap, RSS feed, and Google/Microsoft indexing queue.
3. Content: add or improve one useful asset in News, Blog, Trading Academy, Investing, Personal Finance, and Bitcoin when source/context quality is high enough.
4. Retention: strengthen daily brief, return-tomorrow path, weekly priority update, read-next blocks, section dashboards, and archive links.
5. Trust: update source tracker, source packs, editorial links, correction links, official references, and risk language.
6. Analytics: check GA4, Google Search Console, Bing Webmaster Tools, Microsoft Clarity, Google Trends, PageSpeed, and Lighthouse when access/data exists.
7. Conversion: improve newsletter placement, read-next flow, source-pack CTA, tool CTA, search-to-section route, and contact/support route.
8. Marketing assets: maintain weekly report, monthly report, ETF flow tracker, scam checklist, trading worksheet pack, personal finance checklist, beginner guide, portfolio risk checklist, source verification pack, and best-of page.
9. Quality control: avoid clickbait, fake urgency, spam, misleading headlines, thin pages, repeated claims, and monetization-first pages.
10. Verification: run local checks before sync and deploy once at the end.

Daily marketing asset backlog:

1. Today's Nakamoto Brief: five stories, five sources, five read-next routes, one return action.
2. Marketing Campaigns hub: 30-day Bitcoin, trading, money, investing, scam, stablecoin, and RWA campaigns.
3. Social Share Kit: daily brief post, source thread, mistake-to-avoid, weekly recap, and no-hype distribution copy.
4. Newsletter Archive: daily brief, weekly report, source packs, and returning-reader routes.
5. Best of Nakamoto: curated strongest pages for new visitors.
6. 30-Day Growth Sprints: one campaign, thirty useful daily improvements, one proof trail.
7. Weekly Bitcoin report.
8. Monthly Nakamoto research report.
9. ETF flow tracker improvements.
10. Scam checklist improvements.
11. Trading worksheet pack improvements.
12. Personal finance checklist improvements.
13. Beginner Bitcoin guide improvements.
14. Portfolio risk checklist improvements.
15. Source verification pack improvements.

## Upgraded 100-Point Daily, Weekly, and Monthly Growth Operating System

Use this as the clean master checklist for operations. It is not a demand to finish all 100 items every day. Daily work must cover the four priority sectors first, then use weekly and monthly items on the right cadence.

Default execution rule:

1. Freshness first: update the pages readers expect to be current today.
2. Quality second: improve weak existing pages before adding thin new ones.
3. Discovery third: add internal links, homepage routes, archives, and read-next paths.
4. Measurement fourth: check approved Google and Microsoft data when access exists.
5. Verification last: check locally, fix errors, then sync only when requested or when the command includes sync.

Daily content engine:

1. Update Trading Academy with one useful improvement: lesson, checklist, worksheet, risk note, example, glossary link, or learning path.
2. Update Investing with one useful improvement: ETF context, portfolio explainer, company/source note, market-risk table, or beginner route.
3. Update Personal Finance with one useful improvement: budget, saving, debt, emergency fund, tax-aware note, country guide, or checklist.
4. Update Bitcoin with one useful improvement: beginner guide, custody note, ETF context, mining note, security guide, glossary term, or source path.
5. Update News with fresh, source-checked stories from the last 24 hours when enough real material exists.
6. Update Blog with a useful note, market thesis, editorial explanation, beginner lesson, or source-backed commentary.
7. Preserve old news and old blog posts in dated archives.
8. Add internal links from daily stories into evergreen guides and from evergreen guides back into today's relevant updates.
9. Improve weak headlines without using clickbait, fake urgency, or exaggerated claims.
10. Refresh homepage top stories, Today First routes, and section discovery shelves.

Daily SEO and indexing hygiene:

11. Check `sitemap.xml` after material URL changes.
12. Check `robots.txt` after indexability or crawler changes.
13. Check canonical tags on updated pages.
14. Check page titles for uniqueness, clarity, and search intent.
15. Check meta descriptions for useful summaries and non-duplicated wording.
16. Check image alt text on meaningful images.
17. Check broken internal links.
18. Check broken external links, especially source links.
19. Check duplicate titles, duplicate descriptions, and duplicate article cards.
20. Check orphan pages and add links from hubs, archives, or related articles.

Daily Google and Microsoft growth review:

21. Review GA4 traffic when dashboard data is available.
22. Review Google Search Console impressions when dashboard data is available.
23. Review Google Search Console clicks when dashboard data is available.
24. Review click-through rate and mark low-CTR pages for title/meta testing.
25. Review ranking positions and mark pages near page-one/page-two thresholds.
26. Review Bing Webmaster Tools when dashboard data is available.
27. Review Microsoft Clarity for scroll depth, dead zones, rage clicks, and mobile friction when data exists.
28. Review top pages and add stronger next reads to them.
29. Review weak pages and improve one before adding a weaker new page.
30. Review returning visitors and strengthen daily brief, archives, and newsletter routes.

Daily content quality checks:

31. Improve article introductions so the reader understands the point quickly.
32. Add primary source links where available.
33. Add citations or source notes for important claims.
34. Add practical examples where a topic is abstract.
35. Add FAQs where reader questions are obvious or Search Console query data supports them.
36. Add glossary links for jargon-heavy pages.
37. Add tables where they improve comparison, risk, cost, steps, or source clarity.
38. Add short summaries for long pages.
39. Add read-next links based on topic relevance, not random recency.
40. Remove, correct, or clearly update outdated claims.

Daily user experience checks:

41. Check mobile homepage readability and tap targets.
42. Check mobile article readability and paragraph density.
43. Check desktop homepage hierarchy and above-the-fold clarity.
44. Check navigation labels and remove confusing routes.
45. Check search page usefulness and empty-state recovery.
46. Check newsletter form path, success state, and privacy wording.
47. Check buttons for clear labels, working links, and visible focus states.
48. Check cards for consistent spacing, heading size, and touch behavior.
49. Check footer routes for sources, policies, archives, tools, and priority sections.
50. Check 404 page recovery paths to search, news, guides, tools, and archives.

Daily design and theme checks:

51. Check typography hierarchy: headline, subheading, body, caption, label, and button text.
52. Check spacing rhythm across sections, cards, lists, and article pages.
53. Check contrast in light mode and dark mode.
54. Check dark mode for comfortable long reading.
55. Check light mode for clean, professional, trustworthy reading.
56. Check hover states without relying only on color.
57. Check keyboard focus states.
58. Check images for usefulness, size, loading behavior, and non-decorative alt text.
59. Check icons for consistency, clarity, and visibility in both themes.
60. Check visual consistency against the monochrome, premium, research-publication direction.

Daily performance checks:

61. Run Lighthouse when practical after meaningful design, script, image, or layout changes.
62. Check page speed on important updated routes.
63. Check large images and compress or replace when needed.
64. Check unused scripts before adding more tracking, animation, or embeds.
65. Check CSS size and avoid duplicated visual rules.
66. Check font loading and avoid layout shifts.
67. Check mobile speed because most search/news readers arrive on phones.
68. Check Core Web Vitals when field data exists.
69. Check caching headers after production-readiness changes.
70. Check render-blocking resources before sync.

Daily authority and trust checks:

71. Improve About page when trust signals, editorial scope, or ownership clarity is weak.
72. Improve author and editorial signals on important content.
73. Add or improve editorial standards where source discipline needs proof.
74. Add or improve source policy links.
75. Add or improve correction policy links.
76. Add or improve privacy page routes.
77. Add or improve terms page routes.
78. Add or improve contact route and reader error-reporting path.
79. Add trust signals through source trails, update notes, risk labels, and transparent limitations.
80. Add or improve research methodology where analysis could otherwise feel unsupported.

Daily content discovery checks:

81. Add related articles to updated pages.
82. Strengthen category hubs for Trading Academy, Investing, Personal Finance, and Bitcoin.
83. Surface popular or high-value pages where real data or editorial judgment supports it.
84. Surface evergreen pages that help news readers continue learning.
85. Add latest update blocks to relevant hubs.
86. Add or refresh weekly digest routes.
87. Add beginner paths for complex topics.
88. Add advanced paths for experienced readers.
89. Add comparison pages only when they answer real reader decisions.
90. Add glossary hub links and inline definition links.

Weekly operating layer:

91. Review top 10 pages weekly and improve their next-click paths.
92. Review bottom 10 meaningful pages weekly and improve, merge, or de-emphasize them.
93. Add 10 new article ideas weekly inside Trading Academy, Investing, Personal Finance, and Bitcoin.
94. Review Search Console queries weekly and convert real questions into FAQs, headings, or new guides.
95. Review Microsoft Clarity weekly for mobile friction, ignored sections, and confusing clicks.
96. Review Bing Webmaster Tools weekly after sitemap and important URL updates.

Monthly operating layer:

97. Consolidate duplicate or overlapping content monthly.
98. Refresh old articles monthly with updated dates, source notes, and better links when they materially change.
99. Review analytics setup, sitemap/indexing health, monetization quality, and site structure monthly.
100. Plan next month's content roadmap with priority pages, section upgrades, internal-link targets, and measurement goals.

Operating rhythm: publish, improve, link, measure, fix, and repeat. Fresh news belongs in the daily operation, but only when the story is real, useful, source-checked, and not repeated filler.

Daily operation evidence to record:

1. Pages updated.
2. Fresh news added.
3. Blog update added.
4. Internal links added.
5. SEO files changed.
6. Google/Microsoft checks completed or blocked.
7. Local verification result.
8. Sync status.
9. Remaining issues.
10. Tomorrow's priority.

Priority sectors:

1. Trading Academy
2. Investing
3. Personal Finance
4. Bitcoin

Primary objective: continuously improve content quality, internal linking, navigation, SEO, and user experience across the four priority sectors.

Daily tasks:

1. Improve existing articles before adding weak new pages.
2. Add internal links between related content.
3. Fix broken links and outdated information.
4. Improve article structure, headings, summaries, examples, and readability.
5. Optimize metadata, titles, descriptions, canonicals, schema, and SEO basics.
6. Identify low-quality pages inside the four priority sectors and improve them.
7. Suggest new content opportunities only inside Trading Academy, Investing, Personal Finance, and Bitcoin unless the owner asks for another sector.
8. Maintain consistent Nakamoto tone, design, source standards, and navigation across the website.

Do not:

1. Create unrelated categories.
2. Expand into new sectors unless requested.
3. Prioritize monetization over content quality.
4. Add affiliate links where they are not relevant.

Weekly tasks:

1. Review top-performing pages using approved Google and Microsoft data when available.
2. Improve underperforming pages with better structure, links, metadata, examples, and reader paths.
3. Strengthen category structure for Trading Academy, Investing, Personal Finance, and Bitcoin.
4. Improve navigation and content discovery across the four priority sectors.

Monthly tasks:

1. Upgrade site structure.
2. Improve user experience.
3. Consolidate duplicate or overlapping content.
4. Review overall content quality.

Core philosophy: Update. Improve. Upgrade. Focus on Trading Academy, Investing, Personal Finance, and Bitcoin. Build a high-quality educational platform.

## Extended 1000-Item Growth Backlog

Use `GOOGLE_MICROSOFT_GROWTH_OPERATIONS_1000.md` as the extended daily, weekly, and monthly growth backlog.

Rule: the 1000-item backlog must support the four priority sectors first:

1. Trading Academy
2. Investing
3. Personal Finance
4. Bitcoin

Execution order:

1. Start with the Core Daily Operations Focus in this file.
2. Use the 1000-item backlog for Google Search Console, GA4, Google Trends, PageSpeed, Lighthouse, Bing Webmaster Tools, Microsoft Clarity, Microsoft Promotion, UET, internal linking, metadata, mobile UX, trust, and content discovery.
3. Filter every 1000-backlog task through the four priority sectors before applying it.
4. Do not use the 1000-backlog file to expand into unrelated sectors unless the owner asks.
5. If data is unavailable in Google or Microsoft tools, mark the task as needs data instead of guessing.
6. Record the change, tool used, reason, affected page, and follow-up metric.

Priority sector pages:

1. Trading Academy: `trading-academy.html`
2. Investing: `investing.html`
3. Personal Finance: `money-library/index.html`
4. Bitcoin: `start.html`
5. Site Search: `search.html`
6. Weekly Priority Sector Update: `weekly-priority-sector-update.html`
7. Google and Microsoft Indexing Queue: `priority-sector-indexing-queue.html`

## Operating Rules

1. Preserve old content.
2. Archive daily news by date.
3. Verify every claim with a credible source.
4. Prefer primary sources when available.
5. Use original reporting or official documents when primary sources are not available.
6. Reject weak, vague, copied, fake, or repeated stories.
7. Avoid clickbait.
8. Avoid spam tactics.
9. Avoid black-hat SEO.
10. Avoid misleading headlines.
11. Avoid investment advice.
12. Label uncertainty.
13. Label risk.
14. Keep tone calm, useful, and credible.
15. Optimize every update for long-term reader value.
16. Prepare everything first, then deploy once at the end.
17. Sync to GitLab after execution and checks unless the owner says not to sync.
18. Verify the live GitLab Pages site after syncing.
19. Netlify is only deployable when the Netlify tool/account is available and working.
20. Use https://nakamatoresearch.com as the primary SEO domain for canonical URLs, Open Graph URLs, JSON-LD, RSS, robots.txt, and sitemap.xml.

## Approved Analytics, SEO, Ads, Webmaster, Trends, Performance, and Behavior Stack

Use only Google and Microsoft products for analytics, SEO, Promotion, webmaster tools, trend research, performance analysis, and user behavior analysis.

Approved Google products:

1. Google Search Console
2. Google Analytics 4
3. Google Trends
4. Google PageSpeed Insights
5. Lighthouse

Approved Microsoft products:

1. Bing Webmaster Tools
2. Microsoft Clarity
3. Microsoft Promotion
4. Universal Event Tracking (UET)

Do not use:

1. Ahrefs
2. SEMrush
3. SimilarWeb
4. Moz
5. Any third-party SEO platform
6. Any third-party analytics platform

Growth recommendations must be based only on data from approved Google and Microsoft tools. If the needed data is unavailable, explain what additional setup, verification, dashboard access, waiting period, or manual export is required before making a recommendation.

Use `GOOGLE_MICROSOFT_GROWTH_OPERATIONS_1000.md` as the extended backlog for Google and Microsoft growth, analytics, SEO, Promotion, webmaster, trends, performance, and behavior-analysis operations.

## Hidden Growth Truths To Check During Daily Operations

1. Google rewards consistency slowly; judge early progress by indexed pages, impressions, CTR, and average position before expecting large traffic jumps.
2. Updating old pages with existing impressions can beat writing new pages; check Google Search Console before choosing only new content.
3. Internal links are growth infrastructure; every new or updated article should point readers and crawlers toward the strongest evergreen guides, source pages, desks, archives, and next reads.
4. Thin daily news can hurt trust; publish fewer strong source-checked items when the full 100-item ceiling would require filler, fake freshness, or repeated headlines.
5. Titles and meta descriptions deserve weekly testing; low-CTR pages with impressions should enter the title and meta rewrite log.
6. The homepage is a traffic router, not only a design surface; it should route visitors to today's news, evergreen guides, sources, desks, archives, and the daily brief.
7. Microsoft Clarity may reveal ignored sections, dead zones, rage clicks, and scroll drop-offs; fix what real users ignore even when the section looks good.
8. Bing is a serious secondary search channel; submit and inspect important pages in Bing Webmaster Tools whenever Google indexing work is done.
9. Newsletter and repeat-visit systems protect the site from search volatility; route high-intent readers toward the daily brief, contact form, and thanks-page conversion path.
10. Authority requires proof; keep strengthening the about page, source policy, correction path, author/editor signals, citations, official sources, disclaimers, and original analysis.

## Cost Control Rule

1. Prepare all daily news, main section updates, blog updates, homepage discovery, archive updates, sitemap, feed, and checks before deployment.
2. Run local verification before syncing.
3. Do not push partial work during a normal daily operation.
4. Do not repeatedly sync small corrections during a normal daily operation.
5. Use one final GitLab push and one final Netlify deploy trigger after the operation is complete.
6. If a post-deploy problem is found, fix it carefully, verify locally, and make one correction deploy.
7. This rule protects free-tier usage, reduces build-credit waste, and prevents half-finished live updates.

## Indexing, Trust, and Content Moat Tasks

1. Check whether each important page has a clear purpose; Google does not trust every page equally.
2. Separate indexing from ranking; being indexed is only the first step, not proof that the page can earn traffic.
3. Protect crawl budget by avoiding thin, repeated, low-value, or fake-fresh pages that distract from important routes.
4. Prioritize excellent evergreen guides because one durable guide can outperform many weak daily posts.
5. Preserve clean dated news archives so daily updates remain understandable for readers and search engines.
6. Maintain content hierarchy across hub pages, category pages, guides, news pages, glossary pages, source pages, and tools.
7. Match search intent before chasing search volume; smaller high-intent queries can be more useful than broad vague keywords.
8. Treat low CTR as a title, description, intent, or trust problem to investigate in Google Search Console.
9. Keep mobile pages fast and readable because news and search visitors abandon slow pages quickly.
10. Strengthen trust pages including about, editorial policy, correction policy, contact, privacy, source policy, and disclaimers.
11. Check for broken internal and external links because they quietly damage trust, crawling, and user experience.
12. Avoid duplicate titles and duplicate meta descriptions on important pages.
13. Check canonical tags before publishing because canonical mistakes can hide pages from search.
14. Check noindex and robots rules before sync because one wrong directive can remove important pages from search.
15. Review internal site-search behavior when available because reader searches reveal missing content and unclear navigation.
16. Prioritize returning visitors because repeat readers build direct traffic, brand memory, newsletter growth, and long-term stability.
17. Review the first screen of important pages for trust, clarity, speed, headline quality, and visual credibility.
18. Use structured data where useful, especially Organization, WebSite, Article, NewsArticle, FAQ, and Breadcrumb schema.
19. Keep images useful and lightweight; prefer charts, screenshots, source evidence, and explainers over heavy decorative media.
20. Build a content moat with source discipline, original analysis, archives, tools, explainers, comparison pages, and clear research structure.

## Publication Authority and Brand Growth Tasks

1. Build topical authority through coverage depth in Bitcoin, ETFs, RWA, stablecoins, security, policy, markets, and beginner education.
2. Protect the core money pages even when the site is free: homepage, daily news, Bitcoin guide, ETF guide, RWA guide, safety guide, daily brief page, about page, and source policy.
3. Make daily news feed evergreen assets; every important news update should strengthen a guide, hub, glossary term, source page, or archive.
4. Treat clean archives as a long-term asset that proves consistency, history, and topical depth.
5. Keep reader promises visible: source-checked, plain-English, no hype, no investment advice, and primary sources first.
6. Avoid fighting giant keywords too early; prioritize specific long-tail queries such as Bitcoin ETF flows explained, RWA tokenized stock risks, and seed phrase scam checklist.
7. Maintain multiple entry doors through news, guides, tools, glossary, source pages, archives, category desks, comparison pages, and reports.
8. Improve the about page as a trust asset with editorial standards, correction policy, ownership/contact information, disclaimers, and source policy.
9. Grow glossary coverage for long-tail crypto education, with clear definitions and links into guides, news, tools, and source pages.
10. Build comparison pages for high-intent topics such as Bitcoin versus gold, Bitcoin ETF versus buying Bitcoin, hot wallet versus cold wallet, and stablecoin versus bank deposit.
11. Prioritize tools that can attract links, including calculators, checklists, risk scores, wallet selectors, scam checkers, ETF explainers, and allocation simulators.
12. Add original data where possible through charts, tables, timelines, trackers, source maps, and repeatable measurement pages.
13. Treat email and daily brief subscribers as first-party traffic insurance against search and social platform changes.
14. Track brand search growth for Nakamoto Research as a signal of trust, recognition, and audience memory.
15. Build publication rituals such as daily brief, weekly market review, monthly Bitcoin report, scam watch, ETF flow watch, RWA watch, and policy watch.
16. Give every important page a next action: read next, check source, join brief, use tool, open archive, compare guide, or contact the site.
17. Keep monetization clean; ads and affiliate paths must not make the site feel spammy, cheap, misleading, or unsafe.
18. Treat speed as part of the brand; premium research should feel fast, stable, calm, and clean.
19. Treat design as credibility; messy layouts, weak typography, cluttered sections, and inconsistent visuals reduce trust in the research.
20. Prioritize clarity as the long-term advantage because crypto readers are overwhelmed and need calm explanations they can verify.

## Information Architecture, Editorial UX, and Quotable Asset Tasks

1. Check information scent on links and buttons; users should know what they will get before clicking.
2. Make the first screen answer why the visitor should stay, trust the page, and choose a next path.
3. Build content bridges from beginner pages to news, news to guides, guides to tools, tools to sources, and sources back to topic hubs.
4. Give every category page a reason to exist beyond listing posts: purpose, explainer text, best articles, latest updates, and source links.
5. Put useful summaries before long intros; answer the reader first, then explain the details.
6. Use tables where they improve clarity, especially for comparisons, risks, fees, wallets, ETFs, stablecoins, timelines, and source checks.
7. Build FAQs from real reader questions, Google Search Console queries, internal searches, and Microsoft Clarity friction.
8. Add honest updated dates and change context when important guides are refreshed.
9. Treat corrections as trust-building; make correction paths visible and easy to use.
10. Let topic hubs and guides become long-term ranking pages while news supports them with fresh context and internal links.
11. Pair every tool with an explanatory article, examples, limitations, and FAQ support.
12. Give every article a visible source trail with primary sources, official documents, filings, data, and archive links.
13. Avoid orphan pages; every important page should receive internal links from hubs, categories, archives, or related articles.
14. Create reader levels for key content: beginner, intermediate, advanced, institutional, and professional risk.
15. Avoid samey title formats; repeated headline structures reduce perceived quality and CTR.
16. Keep URLs stable whenever possible; update content instead of changing addresses.
17. Use the footer as discovery infrastructure for hubs, sources, policies, archives, tools, and the daily brief.
18. Make the 404 page useful by routing visitors to search, news, guides, tools, sources, and archives.
19. Give every important page clear ownership: why this page should be the best page on that topic.
20. Make the site quotable with strong definitions, frameworks, checklists, original tables, and source-backed summaries.
21. Add short answer blocks for question-based queries when Google Search Console shows question intent.
22. Add comparison blocks when readers must choose between two approaches, products, risks, wrappers, or routes.
23. Add decision trees where readers need practical next steps instead of only explanation.
24. Add checklists for safety, verification, buying, custody, scams, ETFs, RWA, stablecoins, and research workflows.
25. Add glossary links inside articles so beginners can continue without leaving the site.
26. Add expert-level notes where advanced readers need nuance without confusing beginners.
27. Keep paragraphs short enough for mobile reading, especially in news and guides.
28. Use subheadings that answer real questions instead of vague magazine-style labels.
29. Make introductions specific; avoid generic openings that could fit any crypto site.
30. Make conclusions useful; end with what to watch, what to verify, and where to go next.
31. Add source-quality labels where helpful: official source, filing, data page, research report, regulator notice, company statement, or secondary report.
32. Create original frameworks that can be reused across pages, such as risk ladders, source ladders, custody checklists, and wrapper-risk maps.
33. Review whether each page earns its crawl space; merge, strengthen, or de-emphasize pages that add little value.
34. Make hub pages stronger than tag pages; hubs need editorial structure, not just links.
35. Add read-next modules based on topic relevance, not random recent posts.
36. Add "start here" routes inside complex topics so new visitors are not overwhelmed.
37. Add "latest update" sections to evergreen hubs when fresh news changes the context.
38. Add "source library" sections to major topics so readers can verify claims directly.
39. Add "common mistakes" sections where readers are likely to misunderstand risk.
40. Add "what changed" sections when a page is updated after major regulation, ETF, market, wallet, or security developments.
41. Check that navigation labels match reader language, not internal editorial language.
42. Check whether CTAs are useful and honest; avoid vague commands when a clear next step is better.
43. Make newsletter prompts context-aware; explain why this page's reader should return tomorrow.
44. Use charts and tables only when they clarify decisions; remove visuals that slow the page without helping.
45. Add source screenshots or official-link callouts when a claim is easy to misquote.
46. Add "for beginners" and "for researchers" pathways on dense pages.
47. Add "related risks" links from hype-prone topics such as RWA, stablecoins, AI payments, tokenized stocks, and exchange products.
48. Add "related sources" links from every major guide to primary documentation and trusted reference pages.
49. Check whether important content is buried too low on mobile and move high-value sections higher.
50. Make every daily operation leave at least one page more useful, not merely more recently edited.

## Distribution, Topic Cluster, and Publication Memory Tasks

1. Treat distribution as part of publishing; a page is not complete until it has homepage placement, internal links, sitemap inclusion, RSS/feed support where relevant, Google/Bing indexing path, and a newsletter or return-visit route.
2. Protect the first 48 hours for news; fresh pages should be easy to find from the homepage, news page, archives, related desks, and internal links.
3. Define evergreen update triggers, such as ETF flow spikes, policy changes, new scams, wallet incidents, stablecoin rules, RWA legal changes, mining difficulty moves, and major macro events.
4. Build pillar pages for the site's strongest long-term topics, including Bitcoin basics, ETFs, RWA, stablecoins, wallet safety, regulation, mining, markets, and source verification.
5. Build spoke pages that answer narrow questions and link back to the relevant pillar page.
6. Use topic clusters to prevent random publishing; each new article should strengthen a named cluster or create a justified new one.
7. Give each major cluster a lead magnet, such as a checklist, calculator, email brief, PDF, source list, glossary, timeline, or tool.
8. Control content velocity with quality standards so frequent publishing never looks thin, spammy, copied, or low-trust.
9. Choose battles for a new site by prioritizing long-tail, source-backed, specific topics before broad competitive head terms.
10. Cover repeated topics with useful variation, not duplicate rewrites; each angle should answer a different reader question.
11. Maintain strong article templates with title, summary, why it matters, source trail, related guides, FAQ, next read, and disclosure where needed.
12. Keep the daily briefing format predictable enough to build habit while still allowing editorial judgment.
13. Add "what changed since yesterday" context to daily coverage when a continuing story evolves.
14. Treat trust as cumulative; every source link, correction, archive, update note, and clear explanation strengthens the brand.
15. Use design to reduce cognitive load with less clutter, clearer sections, better spacing, and stronger hierarchy.
16. Use analytics to answer decisions, not to collect dashboards for their own sake; every metric should guide update, remove, promote, test, or wait.
17. Treat good SEO as editorial discipline: helpful organization, clarity, originality, evidence, and trust.
18. Maintain publication memory through logs, archives, update notes, source trails, and dated operation records.
19. Diversify traffic across Google, Bing, direct, newsletter, referrals, and brand search without using unapproved third-party analytics.
20. Optimize for trusted audience growth, not raw traffic alone; the goal is readers who return, share, search the brand, trust the work, and convert.

## Trading Academy Daily Operation Tasks

1. Review the Trading Academy hub and confirm the first screen routes readers to curriculum, market structure, risk lab, glossary, journal, and source standards.
2. Keep Trading Academy education-only language visible on every academy page.
3. Confirm academy pages never contain trade signals, profit promises, personal financial advice, or urgency-driven copy.
4. Add or improve 1-3 high-quality academy learning assets per day when useful: diagram, checklist, calculator, worksheet, FAQ, example, glossary link, study path, case study, or source-backed explainer.
5. Do not bulk-add weak academy pages; quality beats volume for Trading Academy updates.
6. Check that every academy lesson links to the previous lesson, next lesson, academy hub, risk lab, and at least one related source or context page where useful.
7. Improve internal links from news, markets, blog, resources, tools, and beginner pages into the relevant academy lessons.
8. Add academy links back into today's news/blog/finance/economy coverage when a market story needs education context.
9. Check the academy sitemap entries and refresh lastmod dates only when the page genuinely changed.
10. Use Google Search Console URL Inspection for newly added or materially updated academy URLs when dashboard quota allows.
11. Use Bing Webmaster Tools URL Submission for newly added or materially updated academy URLs when dashboard quota allows.
12. Submit or refresh https://nakamatoresearch.com/sitemap.xml in Google Search Console and Bing Webmaster Tools after material academy changes.
13. Check academy pages in Microsoft Clarity after data is available for scroll depth, dead zones, ignored cards, rage clicks, and mobile friction.
14. Check academy pages in GA4 for page views, engagement time, outbound clicks, internal navigation, and returning-reader behavior.
15. Use Google Trends for broad education demand signals such as market structure, trading risk management, chart patterns, support and resistance, and trading journal.
16. Use Google Search Console query data to improve academy titles, descriptions, FAQs, and internal links only when real impressions or queries exist.
17. Keep academy visuals lightweight, readable, monochrome-first, mobile-safe, and accessible.
18. Test academy calculators and interactive elements after every script change.
19. Check academy pages in both light and dark mode for contrast, invisible text, layout shifts, and mobile overflow.
20. Preserve old academy content while improving clarity, structure, links, and examples.
21. Add academy changes to the daily report with pages changed, links added, tools tested, indexing actions, and remaining opportunities.
22. Prepare all academy updates with the rest of the daily operation and deploy once at the end to protect usage credits.
23. Review Trading Academy monetization carefully: keep affiliate links mainly inside `trading-resources.html`, use disclosure before links, add risk context, and route academy pages internally instead of scattering partner links everywhere.
24. When adding trader partner links, check `AFFILIATE_MONETIZATION_LIST.md` first for the approved URL, disclosure rule, and placement strategy.
25. Review live affiliate pages during weekly quality checks: `trading-platforms-comparison.html`, `ftmo-funded-account-review.html`, and `hardware-wallet-comparison.html`.
26. Sync after academy updates and checks unless the owner explicitly says to wait.

## Daily Section Update Rhythm

Use this rhythm when the owner says `Execute daily operation`, `Nakamoto Daily Growth Operation now`, or `Execute full section operation and Google Microsoft growth review`.

1. Update the priority sectors first: Trading Academy, Investing and Finance Library, Personal Finance and Money Library, and Bitcoin.
2. Use News, Blog, Tools, Resources, Search, and the homepage only to support those four priority sectors unless the owner asks for another section.
3. For news-heavy days, publish up to 30 high-quality source-checked items across the most important priority-sector pages before considering any higher-volume target.
4. Keep old news and old guides live; add new context, archives, related links, and updated sections without deleting useful history.
5. Improve at least one discovery route per operation: homepage shelf, section desk, archive, read-next module, footer route, sitemap, or internal link cluster.
6. Run the Google and Microsoft growth review after content is prepared: Search Console, GA4, Google Trends, PageSpeed/Lighthouse, Bing Webmaster Tools, Microsoft Clarity, Microsoft Promotion/UET when available.
7. Record what changed, what was checked, what was submitted for indexing, what needs manual dashboard action, and what should be improved tomorrow.
8. Verify locally before sync.
9. Sync once after the full operation is ready, unless the owner says not to sync.

## Finance and Investing Daily Operation Tasks

Use these tasks for the Finance, Economy, Markets, ETF, Trading Academy, and investor-education parts of Nakamoto Research.

1. Publish or refresh finance and investing updates when real source-backed material exists.
2. For each finance update, include a headline, short summary, source link, why it matters, and reader takeaway.
3. Update the daily briefing routes on the homepage, News page, Finance desk, Economy desk, Markets desk, ETF desk, Blog, Archives, and Newsletters where relevant.
4. Make important finance headlines visible in News, Market Pulse, Search, Archives, and Newsletter paths.
5. Check trusted sources: BLS, BEA, Federal Reserve, Treasury, SEC EDGAR, FRED, company filings, ETF issuers, Investor.gov, official exchange notices, and regulator pages.
6. Refresh market pulse context: valuation, rates, breadth, earnings, risk, liquidity, Bitcoin correlation, ETF flows, and action note.
7. Add or improve one evergreen finance asset when useful: guide, glossary entry, academy lesson, checklist, calculator note, portfolio resource, ETF explainer, or risk framework.
8. Add related links from every finance update to hubs, tools, glossary terms, reports, archives, learning paths, ETF pages, risk pages, and source pages.
9. Prepare newsletter output when useful: daily brief, weekly recap, curated reading path, or market-watch summary.
10. Run quality checks on finance pages: links, buttons, mobile layout, empty cards, accessibility, source visibility, disclaimers, and useful section content.
11. Track workflow status for finance updates: planned, drafted, reviewed, published, updated, archived, refreshed.
12. Preserve older finance content as historical records; refresh with update notes, source links, newer context, and related resources instead of deleting it.
13. Keep dated market notes discoverable through archives, search, categories, topics, related links, and internal links.
14. Avoid price predictions, personalized financial advice, trade signals, profit promises, and urgency-driven investing language.
15. Connect finance stories back to Bitcoin, ETFs, stablecoins, RWA, macro liquidity, policy, cybersecurity, and risk when the connection is useful and source-supported.

## Money Library Daily Operation Tasks

Use these tasks for the personal-finance, budgeting, saving, debt, emergency-fund, retirement, templates, country guides, and financial-literacy parts of Nakamoto Research.

1. Review the Money Library hub and confirm it routes readers to budgeting, saving, debt, emergency fund, financial literacy, investing basics, retirement, templates, tools, countries, and search.
2. Keep all Money Library language educational, calm, and practical; avoid financial advice, pressure, shame, urgency, and profit promises.
3. Add or improve one practical money asset when useful: calculator, checklist, template, country note, FAQ, glossary entry, example, worksheet, or beginner route.
4. Link personal-finance pages back to the Finance Library, Trading Academy, Tools, Search, Resources, and relevant Bitcoin beginner pages where the reader journey naturally continues.
5. Check money tools for clear labels, mobile usability, input readability, privacy wording, result clarity, and useful next steps.
6. Refresh country pages only with current source-backed information; avoid outdated tax, benefits, retirement, or local-rule claims without verification.
7. Improve internal links from finance, markets, tools, resources, homepage, explore, and news desks into the strongest Money Library pages.
8. Keep old money guides live as evergreen education; update intros, source notes, related links, and examples instead of deleting useful pages.
9. Check that Money Library metadata, canonical URLs, sitemap entries, analytics tags, publisher Promotion tag, Clarity tag, and UET tag remain present after updates.
10. Add Money Library changes to the daily report when a page was materially changed or a new internal route was added.

## Evergreen Growth Asset Daily Operation Tasks

1. Review the Bitcoin ETF Flow Tracker for outdated issuer links, changed fee language, new filings, custody changes, flow context, and internal links from ETF news.
2. Review the Stablecoin Risk Dashboard for outdated issuer transparency links, reserve-report cadence, depeg events, redemption language, and policy updates.
3. Review the RWA Issuer Risk Database for new tokenized asset issuers, legal-title questions, regulator status, redemption terms, and source quality.
4. Review the Crypto Security Incident Timeline for new wallet drainer, fake app, phishing, malware, bridge, exchange, or recovery-scam incidents.
5. Add each important daily news item to at least one evergreen growth asset when it improves long-term reader value.
6. Keep these pages source-first: official issuer pages, regulator registers, filings, transparency pages, security advisories, and clear uncertainty labels.
7. Avoid turning trackers into price predictions, trade signals, investment recommendations, or promotional pages.
8. Add internal links from homepage, tools, resources, news desks, RWA pages, stablecoin pages, ETF pages, security pages, and related articles.
9. Check Google Search Console impressions and CTR for these pages once data is available, then improve titles, FAQs, and introductions using only real query data.
10. Submit materially changed tracker pages through Google Search Console URL Inspection and Bing Webmaster Tools when dashboard quota allows.
11. Update the homepage Updated Today shelf whenever the strongest current reader routes change.
12. Review the Weekly Nakamoto Report after daily operations and roll the strongest daily findings into the weekly route.
13. Review the Source Tracker for broken or outdated official links across ETF issuers, stablecoins, RWA regulators, security alerts, filings, and market data.
14. Add new official source links to Source Tracker before relying on them repeatedly in articles or daily reports.
15. Use the weekly report as a returning-reader asset: link it from the homepage, daily brief, source tracker, and relevant daily news updates.

## Quality Control, Risk Prevention, and Editorial Safety Tasks

1. Do not let AI output make the site generic; every article needs a specific angle, source trail, and reader value.
2. Avoid SEO soup pages; do not stuff pages with every keyword when a clearer focused page would serve readers better.
3. Keep freshness honest; use "today," "latest," and dated language only when the page truly reflects current information.
4. Do not over-index weak archives; archives must be useful, organized, and internally linked rather than thin date shells.
5. Give every important page one main job so readers and search engines understand its purpose.
6. Require evidence for every big claim, especially market, legal, security, exchange, custody, policy, and investment-adjacent claims.
7. Separate fact from interpretation; label official facts, reported claims, market reactions, and editorial analysis clearly.
8. Avoid false certainty; use careful wording when outcomes, legal interpretations, prices, or risks are uncertain.
9. Avoid accidental financial advice; provide education, context, and risk framing without telling readers what to buy, sell, or hold.
10. Treat crypto safety content as high-risk; wallet, seed phrase, recovery, scam, exchange, bridge, and custody guidance must be precise.
11. Do not publish copied wording; summarize in original language, limit quotations, and link to sources.
12. Do not chase every trend; cover trends only when they fit the site mission, reader needs, and approved topic clusters.
13. Protect reader attention; avoid too many cards, sections, CTAs, popups, links, and visual distractions on one page.
14. Check visual hierarchy before adding content; more content can make a page worse when structure is weak.
15. Avoid design novelty that hurts reading, speed, accessibility, or trust.
16. Do not bury source links; verification should be easy on every source-first page.
17. Label monetization clearly, including ads, affiliate links, sponsorships, paid placements, or commercial relationships.
   - Keep wallet partner links inside wallet/custody contexts only: `bitcoin-wallet-safety.html`, `resources.html#wallets`, wallet tools, or future wallet comparison pages. Every placement needs disclosure, official-route language, and seed-phrase safety warnings.
18. Disclose uncertainty in breaking news; say what is confirmed, what is developing, and what still needs verification.
19. Avoid legal claims without primary sources; regulation and policy pages should link official documents whenever possible.
20. Protect user trust because one misleading headline can damage the brand more than many good articles can repair.
21. Use a pre-publish trust check for each article: what is confirmed, what is inferred, what is opinion, and what is unknown.
22. Use a pre-publish source check: at least one credible source, preferably a primary source, must support each important claim.
23. Use a pre-publish duplication check so today's article does not repeat yesterday's story without new evidence.
24. Use a pre-publish reader check: the article must answer why this matters and what the reader should verify next.
25. Use a pre-publish risk check for topics involving wallets, private keys, exchanges, taxes, regulation, lawsuits, scams, and tokenized assets.
26. Use a post-publish live check for title, layout, mobile readability, source links, internal links, analytics tags, and sitemap route.
27. Keep claims proportional to evidence; weak evidence should not support strong conclusions.
28. Prefer precise verbs over hype verbs; avoid "explodes," "crashes," "destroys," "guarantees," and similar exaggeration unless literally true.
29. Avoid fear-based headlines that overstate risk, loss, regulation, hacks, or market moves.
30. Avoid greed-based headlines that imply easy money, guaranteed returns, or urgent buying opportunities.
31. Keep educational disclaimers visible on pages that discuss market risk, investing, wallets, tax, legal, or security issues.
32. Add jurisdiction notes when regulation, tax, or legal interpretation varies by country.
33. Add custody-risk notes when discussing ETFs, exchanges, RWA products, stablecoins, bridges, wrapped assets, or tokenized stocks.
34. Add liquidity-risk notes when discussing thin markets, private-market access, tokenized assets, altcoins, or unusual products.
35. Add counterparty-risk notes when discussing issuers, custodians, exchanges, brokers, stablecoin reserves, or payment providers.
36. Add smart-contract-risk notes when discussing DeFi, bridges, automated agents, x402/A402 payments, or on-chain yield.
37. Add operational-risk notes when discussing account access, withdrawal limits, KYC, sanctions, banking rails, and platform downtime.
38. Add security-risk notes when discussing wallet tools, browser extensions, Telegram bots, fake airdrops, recovery services, or support scams.
39. Add source-age checks because old articles, old filings, and old screenshots can become misleading.
40. Add image-evidence checks; screenshots, charts, and graphics should not imply facts that the text cannot support.
41. Add headline-to-body alignment checks; the article must deliver what the headline promises.
42. Add intro-to-source alignment checks; the lead paragraph must not overstate the source material.
43. Add quote-context checks; short quotes must not remove important context or change the meaning.
44. Add correction-readiness checks; each article should have a clear path for readers to report errors.
45. Add update-readiness checks; continuing stories should be easy to update without changing the URL.
46. Add archive-readiness checks; daily pages should remain useful after the news cycle passes.
47. Add source-diversity checks; do not rely only on one weak secondary report for major claims.
48. Add official-source fallback checks; when a primary source is unavailable, say so and avoid overstating.
49. Add conflict-of-interest checks for advertisers, affiliates, sponsored tools, or commercial mentions.
50. Add ad-density checks so monetization does not damage readability, Core Web Vitals, or trust.
51. Add privacy checks for forms, analytics, Promotion tags, and consent-sensitive pages.
52. Add accessibility checks for important content, including headings, labels, contrast, keyboard focus, and reduced motion.
53. Add mobile tap-target checks for navigation, buttons, cards, forms, and filters.
54. Add layout-overflow checks on small screens before syncing important design changes.
55. Add footer-link checks so policies, sources, contact, archives, and major hubs remain discoverable.
56. Add navigation-duplication checks so menus do not repeat links or confuse users.
57. Add broken-form checks for newsletter, contact, thanks page, and Netlify form handling.
58. Add conversion-path checks so high-intent readers can reach the daily brief or contact route without friction.
59. Add analytics-tag checks after major HTML edits to ensure GA4, Clarity, publisher Promotion, Bing verification, and UET remain installed.
60. Add no-payment safety checks for Microsoft Promotion unless the owner explicitly asks to create paid campaigns.
61. Add no-unapproved-tool checks so SEO and analytics work stays within Google and Microsoft products only.
62. Add no-black-hat checks for link schemes, cloaking, doorway pages, scraped content, keyword stuffing, and fake engagement.
63. Add no-spam checks for mass low-value pages, repeated article templates, misleading dates, and artificial freshness.
64. Add no-clickbait checks for titles that create curiosity without delivering real value.
65. Add no-misleading-visual checks for charts, icons, badges, and UI labels that imply authority or status not actually earned.
66. Add no-fake-social-proof checks; do not invent testimonials, traffic, awards, clients, partners, or endorsements.
67. Add no-fake-urgency checks; do not pressure readers with artificial countdowns, scarcity, or alarm.
68. Add no-unverified-performance-claim checks for tools, calculators, models, predictions, and strategies.
69. Add no-medical/legal/tax-advice checks when content touches regulatory, tax, estate, or compliance topics.
70. Add human-usefulness checks: if a page would not help a real reader, it should be improved, merged, de-emphasized, or removed from priority.
71. Add editorial voice checks so articles sound calm, specific, and credible instead of generic, promotional, or robotic.
72. Add paragraph-density checks for long-form pages; dense pages need headings, summaries, tables, and navigation anchors.
73. Add evidence-before-opinion checks for all analysis sections.
74. Add "what would prove this wrong" checks for strong market, adoption, regulatory, or technology interpretations.
75. Add "who benefits" checks for company announcements, product launches, funding news, and sponsored narratives.
76. Add "what can break" checks for every product, wrapper, token, exchange, protocol, wallet, and platform story.
77. Add "reader action" checks that point readers toward verification, safety, learning, or next reading rather than speculation.
78. Add "source trail visible above the fold when appropriate" checks for high-risk or controversial topics.
79. Add "related evergreen route" checks so each daily story helps a long-term page.
80. Add "related archive route" checks so readers can compare how a story changed over time.
81. Add "related risk route" checks for pages that mention custody, leverage, yield, private markets, scams, or regulation.
82. Add "related tool route" checks when a calculator, checklist, or selector can help the reader act safely.
83. Add "related definition route" checks for jargon-heavy stories.
84. Add "reader level" checks so pages do not mix beginner and advanced material without signposts.
85. Add "institutional context" checks for ETF, treasury, custody, RWA, stablecoin, policy, and market-structure content.
86. Add "retail safety" checks for exchange, wallet, scam, and tokenized product content.
87. Add "source freshness" checks for live market, ETF flow, and regulatory pages.
88. Add "chart date" checks so visual data never appears current when it is old.
89. Add "calculator assumptions" checks for tools that estimate returns, allocation, risk, fees, or scenarios.
90. Add "model limitation" checks for forecasts, scenarios, scoring systems, and risk frameworks.
91. Add "AI content disclosure discipline" internally: AI can assist drafting, but the page must pass source, quality, and originality checks.
92. Add "brand consistency" checks for naming, tone, logo use, navigation labels, and editorial promises.
93. Add "premium design restraint" checks so visual polish supports reading instead of turning pages into decoration.
94. Add "performance budget" checks before adding scripts, animations, images, embeds, or heavy effects.
95. Add "ad placement quality" checks so ads do not cover content, break mobile layout, or reduce trust.
96. Add "reader recovery path" checks on dead ends, empty states, search pages, 404 pages, and thanks pages.
97. Add "site memory" checks so important changes are recorded in logs, archives, or operation notes.
98. Add "manual action needed" checks when Google or Microsoft dashboards require owner login, verification, waiting time, exports, or billing decisions.
99. Add "do not sync until ready" checks when changes affect analytics, ads, DNS, indexing, major navigation, or monetization.
100. Add "final verification" checks after sync: live page source, main pages, sitemap, feed, robots, analytics tags, and conversion paths.

## Daily Execution

1. Check today date and UK timezone.
2. Check local project status.
3. Check live GitLab Pages status.
4. Check current news page.
5. Check current blog page.
6. Check operations page.
7. Check homepage Today First, Today Upgrade, scroll/card sections, reader-route cards, source-pack links, and operation links for today's date.
8. Check posted-news log.
9. Check previous archive pages.
10. Preserve old content.
11. Avoid duplicate updates.

## News Coverage

11. Search Bitcoin news.
12. Search Ethereum news.
13. Search Solana news.
14. Search XRP news.
15. Search ETF news.
16. Search RWA news.
17. Search stablecoin news.
18. Search regulation news.
19. Search mining news.
20. Search security and scam news.
21. Search macro and Fed news.
22. Search crypto stocks.
23. Search SpaceX and market-attention news.
24. Search AI-payment and x402 news.
25. Search institutional adoption.
26. Search DeFi news.
27. Search exchange and custody news.
28. Search wallet and self-custody news.
29. Search tokenization news.
30. Search enforcement and court news.
31. Search markets desk stories.
32. Search technology desk stories.
33. Search AI desk stories.
34. Search startups desk stories.
35. Search companies desk stories.
36. Search economics desk stories.
37. Search investing desk stories.
38. Search policy desk stories.
39. Search energy desk stories.
40. Search space desk stories.
41. Search cybersecurity desk stories.
42. Verify sources.
43. Reject weak sources.
44. Reject fake freshness.
45. Reject repeated headlines.
46. Publish up to 100 source-checked items.

## News Desk Category Routes

Every daily operation should decide whether each publication desk needs a fresh update, an internal link, a source check, or no change.

## Priority News Desk Daily Operation Tasks

These eight desks are the core growth routes. Every daily operation must check them before the wider category map.

1. Bitcoin: `news-bitcoin.html` - price context, ETF demand, mining, custody, treasury adoption, macro liquidity, network security.
2. ETF: `news-etf.html` - flows, issuers, fees, custody, SEC filings, fund structure, premium or discount.
3. Economy: `news-economics.html` - inflation, jobs, GDP, rates, dollar liquidity, monetary policy, macro releases.
4. Finance: `news-finance.html` - banks, payments, products, public companies, institutions, market structure.
5. Security: `news-cybersecurity.html` - wallet drainers, phishing, malware, exploits, recovery scams, exchange risk.
6. Stablecoins: `news-stablecoins.html` - reserves, attestations, redemption, payments, regulation, depegs, issuer risk.
7. RWA: `rwa-news.html` - tokenized assets, legal title, custody, liquidity, issuer checks, redemption.
8. Policy: `news-policy.html` - SEC, CFTC, courts, stablecoin law, custody rules, enforcement, market structure.
9. For every daily story, assign one primary desk and one supporting evergreen route.
10. Do not publish thin filler just to reach a number; keep the max at 100, but prefer source-checked quality.
11. Use Google Search Console, Google Trends, GA4, Bing Webmaster Tools, Microsoft Clarity, Microsoft Promotion, and UET only for analytics and growth review.
12. After updating news, refresh internal links from `index.html`, `crypto-news-today.html`, `news-desks.html`, `sitemap.xml`, and relevant evergreen pages.

1. Markets: `news-markets.html`
2. Technology: `news-technology.html`
3. AI: `news-ai.html`
4. Startups: `news-startups.html`
5. Companies: `news-companies.html`
6. Economics: `news-economics.html`
7. Investing: `news-investing.html`
8. Policy: `news-policy.html`
9. Energy: `news-energy.html`
10. Space: `news-space.html`
11. Cybersecurity: `news-cybersecurity.html`
12. Master desk directory: `news-desks.html`

## Whole Website Section Routes

Every daily operation must scan the whole website section list and decide whether each area needs fresh content, better internal links, metadata updates, source links, UI polish, mobile fixes, or no change.

1. Home and discovery: `index.html`
2. Start and beginner path: `start.html`, `chapter-1.html`
3. Explore and reader paths: `explore.html`, `reader-center.html`
4. Daily news and archives: `crypto-news-today.html`, `news-archive.html`, `news-YYYY-MM-DD.html`
5. News desks: `news-desks.html`, all standing `news-*.html` desk routes
6. Blog and daily notes: `bitcoin-blog.html`, `bitcoin-blog-YYYY-MM-DD.html`
7. RWA and tokenization: `rwa-news.html`, `rwa-crypto-explained.html`, `tokenized-stocks-explained.html`, `stablecoins-explained.html`
8. Guides and education: `guides.html`, `more-guides.html`, `faq.html`, `encyclopedia.html`, `encyclopedia-full.html`
9. Research and intelligence: `research.html`, `bitcoin-intelligence.html`, `bitcoin-quant-models.html`, `bitcoin-financial-theories.html`
10. Safety and risk: `bitcoin-wallet-safety.html`, `crypto-scam-checklist.html`, `security-alerts.html`, `risk-center.html`, `bitcoin-decision-safety.html`
11. Tools and calculators: `tools.html`, `calculator-hub.html`, `should-i.html`
12. Markets and ETF: `global-markets.html`, `etf.html`, `bitcoin-etf-explained.html`, `bitcoin-price-scenarios.html`
13. Calendars: `calendars.html`, active `calendar-pages/*.html`
14. Sources and trust: `resources.html`, `data.html`, `bitcoin-trust-systems.html`
15. Growth and retention: `growth-library.html`, `bitcoin-engagement-systems.html`, `daily-brief.html`, `comparison-hub.html`
16. Policy and site trust: `policy.html`, `about.html`, privacy, terms, contact, and support paths when present
17. Operations and deployment: `daily-operations.html`, dated operation archives, `feed.xml`, `sitemap.xml`, `robots.txt`, `publisher file`, `_redirects`, `_headers`, `netlify.toml`
18. Error and utility pages: `404.html`, `thanks.html`, `printables.html`, `timeline.html`, `library.html`, `roadmap.html`, `seo.html`

## Daily Section Update Actions

For every section route above, check the following before calling the daily operation complete:

1. Page loads locally and on the live site after sync.
2. Page has a clear title, description, canonical URL, Open Graph tags, and structured data where useful.
3. Page has working navigation, footer links, CTAs, and read-next paths.
4. Page links to today's strongest relevant coverage when useful.
5. Page has enough helpful text, source links, and context for a first-time visitor.
6. Page has no stale dates, broken references, duplicate cards, placeholder copy, or empty sections.
7. Page reads well on mobile and desktop.
8. Page works in light and dark mode.
9. Page supports content discovery, returning visitors, and search visibility.
10. Page avoids spam, fake freshness, clickbait, and misleading claims.
11. The daily job is not complete until the main section desks are reviewed: Bitcoin, ETF, Economy, Finance, Security, Stablecoins, RWA, and Policy.
12. If today's news touches a main desk, add or refresh a short "Updated Today" block on that desk with today's strongest stories and internal links.
13. Do not say a desk was updated unless the desk page itself was changed or explicitly checked and recorded as unchanged.
14. Finance, Economy, Security, Stablecoins, RWA, and Policy must be treated as active daily sections, not optional leftovers.

## Full Section Operation Checklist

Use this when the owner asks for a full section operation, full website operation, full daily operation, or section-by-section pass. A light operation may check only health, freshness, and urgent issues. A full section operation must inspect each major route group below and record whether it was updated, left unchanged, or blocked.

1. Homepage: check hero, daily story routes, search, reader paths, trust signals, newsletter prompts, design clarity, mobile layout, and links.
2. News current page: check lead story, ranked brief, source trail, related guides, read-next modules, dated archive link, and freshness honesty.
3. News archive: check dated archive links, old-news preservation, duplicate-date risk, and archive discoverability.
4. News desks: check Markets, Technology, AI, Startups, Companies, Economics, Investing, Policy, Energy, Space, and Cybersecurity for purpose, latest route, internal links, and source paths.
5. Blog: check current blog, dated blog archive, analysis quality, source trail, and connection to today's news.
6. RWA and tokenization: check RWA news, RWA explainer, tokenized stocks, stablecoins, custody, issuer, redemption, legal-right, and counterparty-risk links.
7. Guides and education: check start path, chapter 1, guides, more guides, FAQ, encyclopedia, glossary paths, beginner clarity, and read-next paths.
8. Research and intelligence: check research, Bitcoin intelligence, quant models, financial theories, trust systems, source ladder, and original-analysis opportunities.
9. Safety and risk: check wallet safety, scam checklist, security alerts, risk center, decision safety, recovery scam warnings, and custody/security disclaimers.
10. Tools and calculators: check tools, calculator hub, should-I page, form inputs, assumptions, examples, limitations, accessibility, and conversion paths.
11. Markets and ETF: check global markets, ETF center, ETF explainer, price scenarios, macro context, ETF-flow routes, and source links.
12. Calendars: check calendars hub and active calendar pages for useful descriptions, internal links, stale dates, and discovery value.
13. Sources and resources: check resources, data, source links, official references, broken links, source-quality labels, and verification paths.
14. Growth and retention: check growth library, engagement systems, daily brief, comparison hub, newsletter prompts, repeat-visit loops, and brand search support.
15. Policy and site trust: check policy page, about page, editorial standards, corrections, contact, privacy, terms when present, disclosure, and monetization labels.
16. Operations and deployment: check daily operations, dated operation archives, feed, sitemap, robots, headers, redirects, Netlify gate, and GitLab sync status.
17. Utility pages: check 404, thanks, printables, timeline, library, roadmap, SEO page, dead-end paths, and recovery routes.
18. Theme and design: check light mode, dark mode, typography, spacing, contrast, CTA clarity, cards, forms, navigation, footer, and mobile readability.
19. Analytics and webmaster: check GA4, Search Console, Trends, PageSpeed/Lighthouse, Bing Webmaster, Clarity, Microsoft Promotion, and UET only when access/rate limits allow.
20. Final section report: list updated sections, unchanged sections, blocked sections, files changed, checks passed, live URLs, commit hash, and tomorrow's section priorities.

## Editorial Quality

36. Choose lead story.
37. Rank stories.
38. Label high, medium, or low event.
39. Add source verification.
40. Add why it matters.
41. Add reader takeaway.
42. Add what to watch next.
43. Add plain-language context.
44. Add education disclaimers.
45. Avoid investment advice.
46. Avoid clickbait.
47. Avoid hype.
48. Avoid spam.
49. Avoid misleading claims.
50. Create tomorrow watchlist.
51. Check if each story helps readers.
52. Remove weak stories.
53. Keep old news archived.
54. Keep source links visible.
55. Keep repeated themes routed to evergreen pages.

## Page Updates

56. Update `crypto-news-today.html`.
57. Update dated archive page.
58. Update `news-archive.html`.
59. Update `bitcoin-blog.html` and create a dated `bitcoin-blog-YYYY-MM-DD.html` archive when daily news is published.
60. Update `daily-operations.html`.
61. Update homepage.
62. Update RSS feed.
63. Update sitemap.
64. Update posted-news log.
65. Update internal links.

## Desk Checks

66. Check RWA page.
67. Check markets page.
68. Check ETF page.
69. Check security page.
70. Check policy page.
71. Check research page.
72. Check guides page.
73. Check FAQ page.
74. Check tools page.
75. Check calendars page.
76. Check reader center.
77. Check growth library.
78. Check trust systems.
79. Check data page.
80. Check sources and resources page.
81. Check engagement systems.
82. Check comparison hub.
83. Check calculator hub.
84. Check library pages.
85. Check risk center.

## Marketing

86. Surface strongest stories.
87. Improve homepage discovery.
88. Improve category discovery.
89. Surface trending stories.
90. Surface popular stories.
91. Surface evergreen stories.
92. Add related articles.
93. Add read-next links.
94. Add topic tags.
95. Add return-visit hooks.
96. Improve social share copy.
97. Improve RSS visibility.
98. Encourage bookmarking.
99. Improve content recommendations.
100. Improve content clusters.
101. Improve pages per session.
102. Improve session duration.
103. Reduce bounce.
104. Improve visitor trust.
105. Improve beginner onboarding.
106. Turn daily news into long-term traffic.
107. Route daily news into evergreen guides.
108. Add practical checklists.
109. Add source credibility signals.
110. Add topic-hub routes.

## SEO

111. Check titles.
112. Check meta descriptions.
113. Check canonical URLs.
114. Check Open Graph tags.
115. Check Twitter tags.
116. Check JSON-LD.
117. Check sitemap.
118. Check RSS feed.
119. Check robots.txt.
120. Check indexability.
121. Check crawlability.
122. Check duplicate titles.
123. Check stale dates.
124. Check repeated headlines.
125. Check internal anchor text.
126. Check long-tail keyword coverage.
127. Check topic clusters.
128. Check archive discoverability.
129. Check source credibility.
130. Check search intent match.
131. Check homepage title and description.
132. Check category pages.
133. Check article metadata.
134. Check structured-data date fields.
135. Check noindex risks.

## Technical

136. Check local links.
137. Check images.
138. Check scripts.
139. Check styles.
140. Check HTML count.
141. Check page render.
142. Check homepage.
143. Check news page.
144. Check archive page.
145. Check operations page.
146. Check feed.
147. Check sitemap.
148. Run diff check.
149. Run Git status.
150. Remove helper files.
151. Avoid unrelated changes.
152. Check mobile readability.
153. Check text overflow.
154. Check navigation.
155. Check console errors.
156. Check stale domain references.
157. Check broken local targets.
158. Check broken local image paths.
159. Check canonical/live domain alignment.
160. Check deploy-required files.

## Analytics

161. Check unique visitors.
162. Check returning visitors.
163. Check page views.
164. Check top landing pages.
165. Check top exit pages.
166. Check bounce rate.
167. Check pages per session.
168. Check session duration.
169. Check search traffic.
170. Check referral traffic.
171. Check direct traffic.
172. Check RSS traffic.
173. Check popular categories.
174. Check low-performing pages.
175. Check high-performing pages.

## Search Console

176. Check indexed pages.
177. Check excluded pages.
178. Check crawl errors.
179. Check sitemap status.
180. Check impressions.
181. Check clicks.
182. Check CTR.
183. Check average position.
184. Check queries gaining traffic.
185. Check queries losing traffic.
186. Check pages gaining traffic.
187. Check pages losing traffic.
188. Check mobile usability.
189. Check rich result issues.
190. Request indexing when needed.

## Content Strategy

191. Identify content gaps.
192. Build tomorrow story list.
193. Build evergreen article queue.
194. Build glossary queue.
195. Build explainer queue.
196. Build comparison pages.
197. Build beginner guides.
198. Build advanced research pages.
199. Build scam-prevention pages.
200. Build policy explainers.
201. Build RWA explainers.
202. Build ETF explainers.
203. Build mining explainers.
204. Build stablecoin explainers.
205. Build macro and Bitcoin explainers.

## Competitor Review

206. Review competitor headlines.
207. Review competitor topic coverage.
208. Review competitor internal linking.
209. Review competitor category pages.
210. Review competitor archive pages.
211. Find stories competitors missed.
212. Find better angles.
213. Find weak competitor explanations.
214. Build better reader value.
215. Avoid copying competitors.

## Retention

216. Add daily watchlist.
217. Add weekly recap idea.
218. Add newsletter idea.
219. Add RSS callout.
220. Add bookmark hooks.
221. Add glossary links.
222. Add start-here routes.
223. Add related reading.
224. Add safety checklists.
225. Add practical tools.
226. Add archive trails.
227. Add topic hubs.
228. Add return-tomorrow cue.
229. Improve navigation paths.
230. Improve trust signals.

## Trust And Safety

231. Verify every claim.
232. Prefer primary sources.
233. Label uncertainty.
234. Label risk.
235. Add scam warnings.
236. Add custody warnings.
237. Add RWA legal-right warnings.
238. Add stablecoin reserve warnings.
239. Add wallet safety warnings.
240. Add policy uncertainty warnings.
241. Avoid price predictions as fact.
242. Avoid financial advice.
243. Avoid fake urgency.
244. Avoid misleading certainty.
245. Keep correction discipline.

## Deployment

246. Confirm all daily content, main section updates, metadata, sitemap, feed, and local checks are complete before deployment.
247. Stage changes.
248. Commit with `[deploy]`.
249. Push GitLab once.
250. Check deploy status when possible.
251. Verify live homepage.
252. Verify live news page.
253. Verify live archive.
254. Verify live feed.
255. Verify live sitemap.
256. Verify updated text appears.
257. Report final count.
258. Report links.
259. Report checks.
260. Report commit hash.
261. Report sources used.

## Long-Term Growth

262. Build topical authority.
263. Build daily archive depth.
264. Build evergreen library.
264. Build source credibility.
265. Build internal-link graph.
266. Build glossary moat.
267. Build research moat.
268. Build trust moat.
269. Build repeat-reader habit.
270. Build organic search traffic.
271. Grow unique visitors.
272. Grow returning visitors.
273. Grow page views.
274. Grow pages per session.
275. Grow session duration.
276. Reduce bounce rate.
277. Improve rankings.
278. Improve CTR.
279. Improve crawl coverage.
280. Grow toward 1,000,000 unique visitors.

## Daily Idea Bank For Operations

Use these ideas during daily operations when deciding what to publish, refresh, link, test, or measure.

1. Check Google Search Console for pages with impressions but weak CTR.
2. Check Google Search Console for pages ranking near positions 8 to 20.
3. Check Google Search Console for discovered but not indexed pages.
4. Check Google Search Console for duplicate or canonical issues.
5. Check Google Trends before choosing evergreen article topics.
6. Check Google Trends for rising Bitcoin ETF questions.
7. Check Google Trends for stablecoin and RWA demand.
8. Check Google Trends for wallet scam and security demand.
9. Check GA4 for top landing pages.
10. Check GA4 for returning visitor pages.
11. Check GA4 for pages with weak engagement.
12. Check GA4 for newsletter and thanks-page conversions.
13. Check Microsoft Clarity heatmaps for homepage friction.
14. Check Microsoft Clarity recordings for mobile friction.
15. Check Microsoft Clarity for rage clicks and dead zones.
16. Check Bing Webmaster Tools for sitemap and crawl issues.
17. Check Bing Webmaster Tools for indexing parity with Google.
18. Check PageSpeed Insights for homepage mobile performance.
19. Check PageSpeed Insights for article-page mobile performance.
20. Check Lighthouse before keeping heavy animation or visual effects.
21. Refresh one old guide that already has impressions.
22. Improve one page title and meta description from CTR data.
23. Add internal links from today's news to evergreen guides.
24. Add internal links from evergreen guides back to today's relevant news.
25. Add a read-next path to a high-traffic page.
26. Add a source trail to a page that needs stronger proof.
27. Add a short answer block for a question-style query.
28. Add a comparison table where readers need a decision.
29. Add a checklist where readers need practical safety steps.
30. Add a "what changed" note to an updated continuing story.
31. Add a "common mistakes" section to a beginner guide.
32. Add a glossary link where jargon appears.
33. Add a source-quality label to important links.
34. Add a next action to a dead-end page.
35. Improve the footer path to major hubs and policies.
36. Improve the 404 page path if users could get stuck.
37. Strengthen About, corrections, source policy, or contact trust signals.
38. Review ads and monetization for trust, spacing, and mobile safety.
39. Check that publisher Promotion, GA4, Clarity, Bing verification, and UET remain installed.
40. Check that no page accidentally uses noindex unless intended.
41. Check that robots.txt and sitemap still match the intended crawl paths.
42. Check that dated archives preserve old news without duplicate confusion.
43. Check that news pages support topic hubs instead of standing alone.
44. Check that blog updates connect analysis to daily coverage.
45. Check that the homepage routes readers to today's strongest story.
46. Check that category desks have purpose, context, latest updates, and source paths.
47. Check that tools have explanation, assumptions, examples, limitations, and FAQs.
48. Check that financial, legal, tax, security, and custody topics avoid advice.
49. Check that every major claim has evidence proportional to the claim.
50. Check that the day ends with a clear report, commit hash, live links, blocked items, and tomorrow watchlist.

## Reporting Template

After each daily operation, report:

1. Number of items published.
2. Pages updated.
3. Checks passed.
4. Live links.
5. Commit hash.
6. Sources used.
7. Any blocked items.
8. Tomorrow watchlist.

## Research Foundation Daily Operation

Use this after the four priority hubs and before optional traffic-rally expansion. It covers the research foundation sections that strengthen authority, user trust, and long-term search depth:

1. Data & Analytics
2. Statistics
3. Risk Management
4. Economic History
5. Geopolitics
6. Research Methods
7. Tools & Calculators
8. Guides & Tutorials
9. Corporate Finance
10. Capital Markets

Daily rule: choose 2-3 sections and improve one useful thing in each selected section. Do not force all 10 every day.

Daily improvement options:

1. Improve one paragraph.
2. Add one plain-English example.
3. Add one source or source route.
4. Add one internal link to a priority hub.
5. Add one internal link from a priority hub back to the section.
6. Improve one checklist.
7. Improve one tool explanation.
8. Improve one heading.
9. Improve one meta description if needed.
10. Check that wording stays educational and non-advisory.

Section rules:

1. Data & Analytics: update one data point or dashboard route, check one source link, explain what the data means, and link to Bitcoin, markets, investing, or research.
2. Statistics: improve probability, volatility, correlation, base rates, sample size, drawdown, or backtests with a plain-English example.
3. Risk Management: improve one checklist or warning and link to Trading Academy, Bitcoin safety, Investing, or Personal Finance.
4. Economic History: add one historical example, explain similarities and differences, and avoid "history will repeat" claims.
5. Geopolitics: explain one relevant global event through markets, currencies, energy, commodities, or policy without sensational predictions.
6. Research Methods: improve a research checklist, source-quality rule, or fact-vs-interpretation explanation.
7. Tools & Calculators: test or improve one tool, add one "use this when" note, and link back to guides.
8. Guides & Tutorials: improve one tutorial, next-step checklist, beginner path, or guide-to-tool route.
9. Corporate Finance: improve one concept such as cash flow, margins, debt, equity, treasury, valuation, or capital allocation.
10. Capital Markets: improve one concept such as stocks, bonds, ETFs, credit, liquidity, primary markets, or secondary markets.

Weekly operation:

1. Review all 10 research foundation sections.
2. Improve weak pages.
3. Add missing internal links.
4. Check mobile layout.
5. Check metadata.
6. Add one stronger guide, example, source route, or checklist.
7. Confirm all 10 sections are reachable from `sections.html`.
8. Confirm all 10 sections are findable through site search.

Monthly operation:

1. Upgrade the research hierarchy.
2. Add deeper guides.
3. Add better tools or checklists.
4. Merge duplicate topics.
5. Review Google/Microsoft data for clicks, impressions, and rankings when available.
6. Decide which section deserves a full pillar-page upgrade.
7. Review topical authority gaps across data, risk, history, geopolitics, research, finance, and markets.

Rotation:

1. Monday: Data & Analytics + Capital Markets + Risk Management.
2. Tuesday: Statistics + Trading/Risk + Tools & Calculators.
3. Wednesday: Economic History + Macroeconomics + Bitcoin.
4. Thursday: Geopolitics + Commodities + Forex/Currencies.
5. Friday: Research Methods + Guides & Tutorials + Sources.
6. Saturday: Corporate Finance + Business + Investing.
7. Sunday: Review all 10 lightly and improve internal links.

## Executed Daily Operation - 2026-06-28

1. Added `news-2026-06-28.html` with 10 useful source-routed items.
2. Added `bitcoin-blog-2026-06-28.html` with a Sunday editor note.
3. Added `today-source-pack-2026-06-28.html` for the source trail.
4. Added `daily-operations-2026-06-28.html` as the visible operation log.
5. Refreshed `crypto-news-today.html` to show the June 28 daily desk.
6. Refreshed `bitcoin-blog.html` to show the June 28 editor note.
7. Refreshed `daily-operations.html` to show the June 28 operation.
8. Updated `news-archive.html` with June 28 news and operation entries.
9. Updated `feed.xml` with June 28 news and blog items.
10. Updated `script.js` search entries for June 28 news, blog, source pack, and operation page.
11. Updated `sitemap.xml` with June 28 URLs.
12. Preserved the four priority sector rule: Trading Academy, Investing, Personal Finance, and Bitcoin stay central.
13. Added Research Foundation routes into the daily update so Data, Statistics, Risk, and Research Methods support daily quality.
14. No payment processing was added; premium remains a no-payment preview bundle.

### Second-pass priority sector rerun

1. Refreshed `trading-academy.html` with the June 28 risk-first academy route.
2. Refreshed `investing.html` with the June 28 investing route and current operation link.
3. Refreshed `money-library/index.html` with the June 28 money route and removed the stale June 26 block.
4. Refreshed `start.html` with the June 28 Bitcoin route and removed the stale June 26 block.
5. Recorded the rerun in `daily-operations.html` and `daily-operations-2026-06-28.html`.

## Executed Daily Operation - 2026-06-29

1. Added `news-2026-06-29.html` with 10 source-routed items.
2. Added `bitcoin-blog-2026-06-29.html` with the June 29 editor note.
3. Added `today-source-pack-2026-06-29.html` for the source trail.
4. Added `daily-operations-2026-06-29.html` as the visible operation log.
5. Refreshed `crypto-news-today.html`, `bitcoin-blog.html`, and `daily-operations.html` to June 29.
6. Refreshed Trading Academy, Investing, Money Library, and Bitcoin Start with June 29 routes.
7. Updated homepage discovery, news archive, RSS feed, search entries, sitemap entries, and posted log.
8. Preserved the four priority sector rule: Trading Academy, Investing, Personal Finance, and Bitcoin stay central.
9. Locked the visible daily operation pages to the whole-section daily operation rule so future daily work covers the wider section system after the four priority hubs.

## Executed Daily Operation - 2026-07-05

1. Added `news-2026-07-05.html` with 10 source-reviewed Sunday items.
2. Updated `crypto-news-today.html` to the July 5 live desk.
3. Added `bitcoin-blog-2026-07-05.html` and updated `bitcoin-blog.html`.
4. Added `today-source-pack-2026-07-05.html`.
5. Added `daily-operations-2026-07-05.html` and updated `daily-operations.html`.
6. Updated homepage discovery routes for July 5.
7. Updated news archive quick links and archive cards.
8. Updated search entries in `script.js`.
9. Updated RSS feed and sitemap.
10. Updated Google/Microsoft indexing queue.
11. Preserved older July 4 coverage and avoided fake freshness.

## Executed Daily Operation - 2026-07-09

1. Added `news-2026-07-09.html` with 10 source-checked items.
2. Updated `crypto-news-today.html` to the July 9 live desk.
3. Added `bitcoin-blog-2026-07-09.html` and updated `bitcoin-blog.html`.
4. Added `today-source-pack-2026-07-09.html`.
5. Added `daily-operations-2026-07-09.html` and updated `daily-operations.html`.
6. Refreshed Trading Academy, Investing, Money Library, and Bitcoin Start with July 9 daily routes.
7. Updated homepage discovery, news archive, RSS feed, search entries, sitemap entries, source tracker, section dashboard, section archive, indexing queue, and posted log.
8. Preserved older July 8 coverage and avoided fake freshness.


## Executed Daily Operation - 2026-07-10

1. Added `news-2026-07-10.html` with 12 source-checked items.
2. Updated `crypto-news-today.html` to the July 10 live desk.
3. Added `bitcoin-blog-2026-07-10.html` and updated `bitcoin-blog.html`.
4. Added `today-source-pack-2026-07-10.html`.
5. Added `daily-operations-2026-07-10.html` and updated `daily-operations.html`.
6. Refreshed Trading Academy, Investing, Money Library, Bitcoin Start, ETF, Markets, Stablecoins, Policy, Security, RWA, and Finance routes with July 10 daily links.
7. Updated homepage Today First routes, news archive, source tracker, section dashboards, indexing queue, section archives, search entries, RSS feed, sitemap, and posted log.
8. Source set: Economic Times, CoinDesk, Barron's, WSJ, AP, Federal Reserve, BLS, BEA, SEC, CFTC, and Bitcoin Core.
9. Verification required before sync: ad-marker scan, JavaScript syntax, XML parse, dated page link check, git diff check, and live Netlify check after push.


## Executed Daily Operation - 2026-07-11

1. Added `news-2026-07-11.html` with 12 source-checked items.
2. Updated `crypto-news-today.html` to the July 11 live desk.
3. Added `bitcoin-blog-2026-07-11.html` and updated `bitcoin-blog.html`.
4. Added `today-source-pack-2026-07-11.html`.
5. Added `daily-operations-2026-07-11.html` and updated `daily-operations.html`.
6. Refreshed Trading Academy, Investing, Money Library, Bitcoin Start, ETF, Markets, Stablecoins, Policy, Security, RWA, and Finance routes with July 11 daily links.
7. Updated homepage Today First routes, news archive, source tracker, section dashboards, indexing queue, section archives, search entries, RSS feed, sitemap, master operations page, and posted log.
8. Source set: Economic Times, CoinDesk, Circle, AP, Federal Reserve, BLS, BEA, SEC, CFTC, and Bitcoin Core.
9. Verification required before sync: ad-marker scan, JavaScript syntax, XML parse, dated page link check, git diff check, and live Netlify check after push.


## Executed Daily Operation - 2026-07-12

1. Added `news-2026-07-12.html` with 12 source-checked items.
2. Updated `crypto-news-today.html` to the July 12 Sunday source review.
3. Added `bitcoin-blog-2026-07-12.html` and updated `bitcoin-blog.html`.
4. Added `today-source-pack-2026-07-12.html`.
5. Added `daily-operations-2026-07-12.html` and updated `daily-operations.html`.
6. Refreshed Trading Academy, Investing, Money Library, Bitcoin Start, ETF, Markets, Stablecoins, Policy, Security, RWA, and Finance routes with July 12 daily links.
7. Updated homepage Today First routes, news archive, source tracker, section dashboards, indexing queue, section archives, search entries, RSS feed, sitemap, master operations page, and posted log.
8. Source set: Economic Times, CoinDesk, Circle, AP, Federal Reserve, BLS, BEA, SEC, CFTC, and Bitcoin Core.
9. Verification required before sync: ad-marker scan, JavaScript syntax, XML parse, dated page link check, git diff check, and live Netlify check after push.


## Executed Daily Operation - 2026-07-13

1. Added `news-2026-07-13.html` with 12 source-checked items.
2. Updated `crypto-news-today.html` to the July 13 live desk.
3. Added `bitcoin-blog-2026-07-13.html` and updated `bitcoin-blog.html`.
4. Added `today-source-pack-2026-07-13.html`.
5. Added `daily-operations-2026-07-13.html` and updated `daily-operations.html`.
6. Refreshed Trading Academy, Investing, Money Library, Bitcoin Start, ETF, Markets, Stablecoins, Policy, Security, RWA, and Finance routes with July 13 daily links.
7. Updated homepage Today First routes, news archive, source tracker, section dashboards, indexing queue, section archives, search entries, RSS feed, sitemap, master operations page, and posted log.
8. Source set: CoinDesk, Economic Times, Circle, AP, Federal Reserve, BLS, BEA, SEC, CFTC, and Bitcoin Core.
9. Verification required before sync: ad-marker scan, JavaScript syntax, XML parse, dated page link check, git diff check, and live Netlify check after push.


## Executed Daily Operation - 2026-07-14

1. Added `news-2026-07-14.html` with 12 source-checked items.
2. Updated `crypto-news-today.html` to the July 14 live desk.
3. Added `bitcoin-blog-2026-07-14.html` and updated `bitcoin-blog.html`.
4. Added `today-source-pack-2026-07-14.html`.
5. Added `daily-operations-2026-07-14.html` and updated `daily-operations.html`.
6. Refreshed Trading Academy, Investing, Money Library, Bitcoin Start, ETF, Markets, Stablecoins, Policy, Security, RWA, and Finance routes with July 14 daily links.
7. Updated homepage Today First routes, news archive, source tracker, section dashboards, indexing queue, section archives, search entries, RSS feed, sitemap, master operations page, and posted log.
8. Source set: CoinDesk, BLS, Federal Reserve, House Financial Services, Senate Banking, Circle, and Bitcoin Core.
9. Verification required before sync: ad-marker scan, JavaScript syntax, XML parse, dated page link check, git diff check, and live Netlify check after push.


## Executed Daily Operation - 2026-07-15

1. Added `news-2026-07-15.html` with 12 source-checked items.
2. Updated `crypto-news-today.html` to the July 15 live desk.
3. Added `bitcoin-blog-2026-07-15.html` and updated `bitcoin-blog.html`.
4. Added `today-source-pack-2026-07-15.html`.
5. Added `daily-operations-2026-07-15.html` and updated `daily-operations.html`.
6. Refreshed Trading Academy, Investing, Money Library, Bitcoin Start, ETF, Markets, Stablecoins, Policy, Security, RWA, and Finance routes with July 15 daily links.
7. Updated homepage Today First routes, news archive, source tracker, section dashboards, indexing queue, section archives, search entries, RSS feed, sitemap, master operations page, and posted log.
8. Source set: CoinDesk, BLS, and Bitcoin Core.
9. Verification required before sync: ad-marker scan, JavaScript syntax, XML parse, dated page link check, git diff check, and live Netlify check after push.

## Executed Daily Operation - 2026-07-16

1. Added `news-2026-07-16.html` with 12 source-checked items.
2. Updated `crypto-news-today.html` to the July 16 live desk.
3. Added `bitcoin-blog-2026-07-16.html` and updated `bitcoin-blog.html`.
4. Added `today-source-pack-2026-07-16.html`.
5. Added `daily-operations-2026-07-16.html` and updated `daily-operations.html`.
6. Refreshed Trading Academy, Investing, Money Library, Bitcoin Start, ETF, Markets, Stablecoins, Policy, Security, RWA, AI Finance, Economy, Finance, and Bitcoin desk routes with July 16 daily links.
7. Updated homepage Today First routes, news archive, source tracker, section dashboards, indexing queue, section archives, search entries, RSS feed, sitemap, master operations page, and posted log.
8. Preserved older daily archives and source packs.
9. Verification required before sync: JS syntax, XML parse, local link scan, stale-current-route scan, ad-code scan, diff check, GitLab push, and Netlify live check.

## Executed Daily Operation - 2026-07-18

1. Added `news-2026-07-18.html` with 12 source-checked items.
2. Updated `crypto-news-today.html` to the July 18 live desk.
3. Added `bitcoin-blog-2026-07-18.html` and updated `bitcoin-blog.html`.
4. Added `today-source-pack-2026-07-18.html`.
5. Added `daily-operations-2026-07-18.html` and updated `daily-operations.html`.
6. Refreshed Trading Academy, Investing, Money Library, Bitcoin Start, ETF, Markets, Stablecoins, Policy, Security, RWA, AI Finance, Economy, Finance, Bitcoin desk, and desk directory routes with July 18 daily links.
7. Updated homepage Today First routes, news archive, source tracker, section dashboards, indexing queue, section archives, search entries, RSS feed, sitemap, master operations page, and posted log.
8. Preserved older daily archives and source packs.
9. Verification required before sync: JS syntax, XML parse, local link scan, stale-current-route scan, ad-code scan, diff check, GitLab push, and Netlify live check.

## July 19, 2026 Daily Operation

1. Added `news-2026-07-19.html` with 12 source-checked items.
2. Updated `crypto-news-today.html` to the July 19 live desk.
3. Added `bitcoin-blog-2026-07-19.html` and refreshed `bitcoin-blog.html`.
4. Added `today-source-pack-2026-07-19.html`.
5. Added `daily-operations-2026-07-19.html` and updated `daily-operations.html`.
6. Refreshed homepage, daily master checklist, daily dashboard, indexing queue, source tracker, section archive, RSS, sitemap, and search entries.
7. Refreshed Trading Academy, Investing, Money Library, Bitcoin Start, ETF, Markets, Stablecoins, Policy, Security, RWA, AI Finance, Economy, Finance, Bitcoin desk, and desk directory routes with July 19 daily links.
8. Preserved older daily archives and source packs.