Why does my map have fewer pages than its size?

Three things decide how many pages a map holds.

How many attributes the subject has

The map is built from attributes of the central entity and the core topics, mined from Wikipedia and Wikidata, Google autocomplete, the stored People Also Ask questions, competitors' sitemaps and your profile. A broad subject with rich sources yields several hundred; a narrow one yields fewer. Every mined attribute is listed with its source, and the ones dropped as outside the border or duplicates are dropped with a reason. A map cannot hold more pages than the subject has attributes worth a page.

How many pass the page test

Each candidate topic gets a results page and the four checks: demand, a distinct entity and attribute, results unlike the pages already accepted, a clear query pattern. Three of four make a page. Topics whose results are the same as another page's fold into it as headings. See Why did a topic become a heading?.

The size

The pages that pass are kept up to the size: 60, 150 or 300. Any beyond that, and any candidates the run did not test, are shown under In reserve on the Map tab, so you can see what a larger size would have added.

What you paid for

The price is the size, whatever the subject yields. A Large map that comes out at 217 pages still cost 900 credits, because the mining, the results pages, the page tests and the inspection of 60 core pages were all done at the Large scale. If the reserve list is empty, the map already holds every page the subject earned, and a larger size would not have added any.

Getting more pages

• Widen the centre on a new version: add a core topic that is part of the subject, or move something from the border into the core topics.
• Add encyclopedia topics that have an article, so the mining reads more sources.
• Add competitors in Settings; their sitemaps are a source of attributes.
• Run the site research first if you have not: its People Also Ask questions feed the mining.