Sites Q&A section pagination structure

[rivsrush]

Hi!

Sites Q&A page became a bit long so time had come to split it to multiple pages.
How you suggest to move in term of pagination structure. Below is a few variants we are considering.
Very appreciate your input.
Thank you!

---------// Variant 1 //--------
[root]\qa01.html
[root]\qa02.html
[root]\qa0n.html
---------// Variant 2 //--------
[root]\qa\01.html
[root]\qa\02.html
[root]\qa\0n.html
---------// Variant 3 //--------
[root]\qa\page\1
[root]\qa\page\2
[root]\qa\page\n

[Dimitri]

I prefer the first variant, the shortest the URL, the better (but it's only personal opinion)

[lucy24]

Personally I like #2. Any time there is an URL in the form
/stuff/more/stillmore
you should stop and ask whether there exists, or could exist, a page called simply
/stuff/more/
and-that's-all. If there is no such page, your URL structure has too many layers.

It helps to think of them as physical directories, regardless of how the pages are actually created. If a given directory--or “directory”--never will, and never could, contain more than one page, then that “page” doesn’t require a name.

There are very, very few situations where the form
title/page/1
title/page/2
(using that actual word “page” or similar) isn't silly. Almost by definition, the URL
title/page/
and-that's-all can't exist.

[rivsrush]

Thank you Dimitri.
Lucy24, agree with your opinion. What about [more results] button status, compare "hard" coded pages links/buttons.

[tangor]

When you say the page "became a bit long", what does that mean?

Too many words, or too many FAQ entries?

If the word count is over 100k (that's WORDS, not bytes), then maybe a breakup is reasonable. Else I'd keep it all on one page and ensure that in-page navigation was the best it can be. Put a table of contents at the top listing the sections and make sure there's a return or jump for each section.

With today's speeds that once loaded all-in-one page will navigate even faster than moving to sub pages.

[rivsrush]

Got you tangor, great hear from you :)
Yes, it is number of FAQ entries - Number of words - height of html body.
Sounds like keep it simple.

[tangor]

In most cases I ignore "height of html body" as the user only sees one screen at a time, ie "a page". Properly structured a 275,000 word document is as easy to navigate as 27,500 1000 word individual pages. Actually easier. :)

A table of contents structure is your best friend.

MEANWHILE, FAQ, in particular, should have categories to group inquires/interest. Those can be top head (hidden sub) in css, click the plus sign and see what's inside.

THAT SAID, if you actually have THAT MANY CATEGORIES/ITEMS then there's no hope to satisfy ... just means your visitors have no clue when they arrive!

Answer the big questions/confusion first, only go into detail if necessary. After all, your content should be explanatory in the first place.

[rivsrush]

Fair enough tangor, great answer, what amazes me is that g* just came out, about a week ago, with a new update of structural schema specs - FAQ and How-To. Your answer is essentially reflected on what is in ;)
Thank you very much for help!

[tangor]

about a week ago, with a new update of structural schema specs - FAQ and How-To. Your answer is essentially reflected on what is in ;)

Post a link ... g and I rarely agree on anything!

Actually, just kidding. Keep FAQs short and to the point. That has always been the best method. Most times you deal with the top 10 most asked questions, maybe the top 15 ... any more than that and you are either in a very tough niche/topic or deal with users without a clue, or---worse---your content is not complete enough to answer the questions in the first place.

All good luck on updating your FAQ!

[RhinoFish]

var2.
So many things require rule writing... htaccess, AdSense site sections, Audience remarketing scripts, Analytics Content Grouping, and on and on... structuring like var2, gives you easier rule writing and enforcement.
And, your "qa" case seems easy, but wait until "be" and other non-trivs gunk things up.

[rivsrush]

RhinoFish - thank you for comment.
Tangor - I heard that fact about you:) fyi link to official doc and yt faq,
Thank you again!

[developers.google.com...]
[support.google.com...]

[rivsrush]

To all have a good holiday!