Who, how, and why
Content for the operating decision, not the crawler.
Aptoria’s product and editorial team is responsible for the public library. Pages are written for small landlords and property operators who need to understand a record, make a bounded decision, or complete a workflow. The reason for publishing is to make that job safer and clearer—not to manufacture coverage for every way a query can be phrased.
Aptoria may use AI-assisted tools to research candidate topics, compare source material, draft or edit text, create code, and run repository checks. AI assistance is not treated as authority or independent experience. Claims, links, examples, functionality, overlap, and publication status are reviewed against the repository’s explicit gates; sensitive material stays unpublished until its source and reviewer requirements are met. Current review records may identify a Codex-assisted repository audit and should not be read as a named lawyer, accountant, or human subject-matter expert sign-off.
The six-step publication path
1
Choose the user job
Start from a recurring landlord decision, operating record, failure, or control—not a list of keyword variants.
2
Check ownership
Search the existing library and assign one canonical page to the intent. Consolidate aliases and closely related questions.
3
Build the evidence set
Use primary law, government, standards, product, or provider sources when a claim needs support; record limits and uncertainty.
4
Create the artifact
Add a scenario, worksheet, calculation, diagram, comparison, decision frame, or control that helps the reader do the work.
5
Run publication checks
Test originality, depth, links, metadata, schema-to-visible-content parity, functionality, and crawl boundaries.
6
Review and maintain
Record the review date and reason. Update the page when its facts or method change—not to manufacture freshness.
Fail-closed review
Index, hold, consolidate, or retire.
New glossary expansions and guides do not become indexable merely because a file exists. Missing positive review records remain noindex and stay out of hubs and sitemaps.
One distinct job
The page answers a decision or task not already owned by another canonical page.
It exists mainly for a query, synonym, location, or product variation.
Original operating value
It adds a worked example, field map, decision rule, tool, visual, failure mode, or source analysis.
It rearranges familiar definitions or repeats the same template with changed nouns.
Evidence fit
Claims use appropriate primary sources, visible limitations, and review boundaries.
Legal, tax, financial, local, pricing, or product claims lack authoritative support.
Usable and connected
The page works, is readable, has complete metadata, and is linked from a real hub and related pages.
A promised tool does not function, links are missing, or the page is discoverable only through a sitemap.
Sources and sensitive subjects
Primary sources are preferred for law, government guidance, technical standards, and product behavior. A citation supports only the claim it actually establishes; broad standards are not presented as property-law authority. Legal, tax, screening, fair-housing, deposit, local, financial, and vendor-comparison pages receive tighter boundaries and may remain noindex until the appropriate source or qualified review exists.
Examples use stated hypothetical facts unless the page identifies a source. Calculators explain inputs, formulas, outputs, and limitations. Structured data mirrors visible content and does not turn a weak page into a stronger one.
Corrections, updates, and removal
A substantive change can update the visible review date. A formatting change alone does not. Pages can be consolidated when intent overlaps, held from search when evidence is incomplete, or removed when they no longer serve a distinct user job. For a correction, send the URL, disputed statement, supporting source, and requested change through Aptoria contact.