USPTO releases the weekly Patent Grant Bibliographic Data file every Tuesday, and PatentsView refreshes on a similar cadence. Most SleekRank patent setups use a 7-day cache for individual records and re-import the bulk feed weekly. New grants appear on the site within one cache window of the USPTO drop.

Yes, but claims pages get large. Most teams render the abstract and first independent claim on the main per-patent page, then add a /patent/{slug}/claims/ child page group for the full claims text. The detailed description is typically linked out to the USPTO PDF rather than mirrored.

Run them as separate page groups since the data shape differs. Design patents use D-prefixed numbers and image-heavy templates; plant patents use PP-prefixed numbers and botanical fields. Same plugin, three configs, three URL patterns - /patent/, /design-patent/, /plant-patent/.

Create a second page group for assignees keyed by assignee name or NDC, and a third for inventors keyed by normalized name. Then in the patent template, use selector mappings to render the assignee field as a link to /assignee/{slug}/. The three corpora interlink without duplicating data.

The PatentsView feed reflects reassignment in subsequent updates, so the assignee field will refresh after the cache expires. Invalidated patents are usually still indexed at USPTO but flagged. Add a status field, use a selector mapping to show an invalidation banner, and let the existing page persist for the citation graph.

Google Patents is the consumer face of USPTO data with their own search interface and ranking. Scraping is fragile, against their terms, and gives you no rights to redistribute. PatentsView is a public USPTO-funded research dataset with explicit redistribution rights, and SleekRank reads it directly without intermediation.

Yes. Use a separate WordPress post type or a notes column in a secondary spreadsheet keyed by patent number. SleekRank can merge a secondary source on the same slug and render expert commentary alongside the official record. The commentary stays editable in WordPress; the bibliographic data stays bound to the bulk feed.

SleekRank stores each resolved record as a row in wp_sleek_rank_items, roughly 2-5 KB per patent depending on field length. Eleven million records is a 30-60 GB MySQL footprint, manageable on a single dedicated database server. Most production setups start with a CPC-class subset and scale up.